Server-side filtering for NodeNetworkConfig, Node, and Pod objects #1198
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.
Signed-off-by: Evan Baker rbtr@users.noreply.github.com
Reason for Change:
Instead of watching all NNCs (and Nodes and Pods) and filtering on the client-side, we should modify the Manager's cache to only Watch objects with the appropriate fields set which match our Node. This filtering happens server-side as part of the WatchList initialization and should effectively scope CNS's apiserver traffic to its own Node's objects instead of letting it scale with Node and Pod count.
Issue Fixed:
Requirements:
Notes: