-
-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select kube-vip instance by LoadalancerClass #791
Comments
+1, but you have also to change add a parameter to set the lease name, because the kubevip instance uses a standard name (plndr-svcs-lock) for all instances. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using two instances for the private/public interfaces. Currently I'm deployed them to separate namespaces and they listening their namespace only.
Now I have more namespace which needed vip, but this config will not handle it. I found the ticket about the LoadbalancerClass, It now restrict kube-vip to one label key. #413 witch not far to solve this problem.
If the label not static, but configurable via env I can deploy multiple kube-vip checking all namespaces but the instances restricted to their configured LoadbalancerClass. I think this can be more flexible/useable.
The text was updated successfully, but these errors were encountered: