Issue #1595 --Part1-- Add fieldSelector in listWatchFunc #1596
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Since we want to add namespace deny list, we need to to propagate the namespace denylist all the way down to the listwatchers, this is especially helpful when namespaces is "", more details see discussion here: #1595.
Once this PR is merged, we can go back to PR 1595 and continue do the rest of the changes.
In this PR I am trying to add a fieldSelector for opts, later we can pass this value in main function, where we use the namespaceDenyList to get the fieldSelector.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Details: #1593