Update kube-router network policy controller #2867
Merged
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.
Proposed Changes
Update network policy controller code to resync with kube-router: v1.0.0-rc2 -> v1.1.1 (master)
cloudnativelabs/kube-router@d6f9f31...ee9f6d8
Types of Changes
bugfix/upstream
Verification
Run normal test suite
Linked Issues
#2876
Further Comments
This update pulls in several bug fixes and a restructuring of the code from upstream. I have attempted to minimize the number of changes to the upstream code in order to make future resyncs easier. This includes modifying our Run wrapper to set up and sync the shared informers similar to how upstream's controller setup does it.
Most of the changes are limited to:
CLI configuration, eliminate use of a WaitGroup for shutdown sequencing, and drop Prometheus metrics support.
The updated network policy controller also wants to know about a couple new cluster-level configuration items, such as the cluster service CIDR range and the node-local port range, so those need to be plumbed through.