-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
kubernetes endpoints topology.kubernetes.io/zone affinity #7983
Comments
Hey @sylr, thanks a lot for your request. Currently, topology is only available in alpha mode since K8s 1.17, as you probably know. For that reason, its not available on most (if not all) cloud provider k8s installations and thus, it's by itself only available to a very limited subset of K8s end users. Also, as its in alpha, its still subject to change with new KEPs being available to fully discard that feature and work on something new. For that reasons, we currently don't plan to implement topology zone support. However, it the feature will by itself will move past the alpha flag, we might reconsider our options. I'll keep the issue open as a proposal to gather general interest :) |
We are very interested in this feature as well. Topology Aware Hints are now beta as of Kubernetes 1.23 |
Any news here? In 1.27 the feature was rennamed: Until treafik supports it we are forced to use the nativelb treaefik setting. |
@runningman84 Does topology aware routing works with nativelb in your setup? It doesnt make any difference in ours somehow. Any ideas what I may be doing wrong? |
In our setup it works you, in a 3 zone setup you have to have at least 9 pods otherwise it falls back to the normal routing. |
FWIW: #10664 is the first required step towards implementing this; anyone interested is free to look into/contribute to that. |
Do you want to request a feature or report a bug?
Feature
What did you expect to see?
It would be nice if Traefik would allow to favor endpoints living in the same
topology.kubernetes.io/zone
as itself in order to avoid the additional cost of sending traffic to endpoints living in a different zone. The endpoints in other zones would only be used as fallback when none is available in the same zone.Regards.
The text was updated successfully, but these errors were encountered: