Skip to content
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

Open
cfillot opened this issue Jul 15, 2023 · 7 comments
Open

Egress IP with AZ affinity #5252

cfillot opened this issue Jul 15, 2023 · 7 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. reported-by/end-user Issues reported by end users.

Comments

@cfillot
Copy link

cfillot commented Jul 15, 2023

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.

@cfillot cfillot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 15, 2023
@tnqn
Copy link
Member

tnqn commented Jul 17, 2023

This is not supported yet, but we can think about how to improve. May I know what platform is the cluster run on?

@cfillot
Copy link
Author

cfillot commented Jul 18, 2023

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).

@pdaccache
Copy link

Hi plz can u advise how to make it work on aws? It is not outgoing using egressip, always using node ip

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2023
@tnqn tnqn removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 26, 2023
@tnqn tnqn added the reported-by/end-user Issues reported by end users. label Dec 11, 2023
Copy link
Contributor

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

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2024
@tnqn tnqn removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2024
Copy link
Contributor

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

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 10, 2024
@tnqn tnqn removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 12, 2024
@antoninbas
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. reported-by/end-user Issues reported by end users.
Projects
None yet
Development

No branches or pull requests

4 participants