-
Notifications
You must be signed in to change notification settings - Fork 368
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
Egress IP with AZ affinity #5252
Comments
This is not supported yet, but we can think about how to improve. May I know what platform is the cluster run on? |
Thanks a lot for your answer. It is a bare metal cluster running Kubernetes v1.26, Antrea v1.11.1 and MetalLB 0.13.9 (Debian Linux 11). |
Hi plz can u advise how to make it work on aws? It is not outgoing using egressip, always using node ip |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days |
I have opened a parent issue for this request (#6591), and it's a bit more generic and more detailed. But we can keep this one open as well for now. |
Hello,
I have different AZ with a specific subnet for egress in each AZ. I create an External IP pool for each AZ with a node selector based on zone label.
If I create many Egress IPs matching the same namespace and bound to each IP pool, an Egress IP is selected randomly, and exit traffic for an AZ can go through another AZ. It works, but unfortunately it's suboptimal and I would like that pods running in an AZ use the "local" Egress IP.
Is it possible to do something like that ? If not, is it a planned feature ?
Thanks for a lot for any suggestion.
The text was updated successfully, but these errors were encountered: