Add lb_class_only env var to restrict ips for LB class only #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Rahul Ganesh <[email protected]>
|
Hey @rahulbabu95 , thank for opening this. This functionality is already available via |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Kube-vip deployed by this chart is also trying to manage LoadBalancer IPs of any external service requesting for a LB IP. Ideally kube-vip should only manage IPs for those services that have LoadBalancerClass set to kube-vip.io/kube-vip-class on the service. This change adds the necessary env in the kube-vip config to only manager the LB Ips for the services with LB class set.
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: