fix: kube-proxy collides with kubevip #197
Open
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.
As raised in #192. Kube-proxy will remove networking configuration for it's pod CIDR that it does not manage. In the instances where our kube_vip_loadbalancer CIDR overlaps with the pod CIDR this will cause failures to provision a virtual IP for Loadbalancers.
See: https://kube-vip.io/docs/about/architecture/#known-issues