-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Request]: Static IP LoadBalancer #42
Comments
Thanks for the query. Currently this feature is already supported since this feature request . You need to use a similar yaml structure.
As you can see, there is no need to use annotation in case of loxilb. Just use standard field "externalIPs". The staticIP provided can be part of LB IPAM subnet or completely different. |
PR - Dont re-add staticIP back to ingress even if it is in LBIPAM range
|
Due to a known issue of kube-proxy(ipvs), static IP does not work with loxilb.io/lbmode: "fullnat" mode. But it should work fine for loxilb.io/lbmode: "onearm". As per your topology explained in other issue, one arm should work fine. This issue is fixed for non static IP but for static IP, it is better to use one-arm mode. |
Yes onearm is working properly, Thank you. |
Dear loxilb team,
We would like to request static ip LoadBalancer from ippool , due to some application which exposed via LoadBalancer is being used by third party direct ip connection and not used domain, so if ip LoadBalancer changed it will take a long time to sync with third party caused by administration process that will take place just to change the ip LoadBalancer,
If it's possible we want some configuration used by cilium:
With this annotation cilium can directly assign static ip 172.24.25.211 from the ippool,
loxilb team are awesome and mind blowing,
Thank you
The text was updated successfully, but these errors were encountered: