You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realized, Ingresses won't necessarily respect this bc by design their controllers usually watch Endpoints directly to determine what pods are healthy, etc. for routing.
https://stackoverflow.com/a/63402311 suggests if controllers leverage EndpointSlices instead over time, that they could support topology-aware routing.
Without having time to read the code currently, I wanted to clarity on if
does the controller use EndpointSlices at all (I saw some issues that referred to them when searching) and therefore does topology-aware routing work ?
And 2) if not, is this an enhancement that can be added to the roadmap for v0.16 ?
Thanks for your time/hard work, and looking forward to chatting more on this. Cheers.
The text was updated successfully, but these errors were encountered:
onelapahead
changed the title
[question] EndpointSlices and Topology-Aware Routing
[question] [enhancement] EndpointSlices and Topology-Aware Routing
Dec 12, 2024
Hello, thank you for the awesome controller. We're using it with great success for all of our clusters currently.
We're looking to cut our network costs in the cloud by leveraging https://kubernetes.io/docs/concepts/services-networking/topology-aware-routing/ for internal comms btwn our
Services
.I realized,
Ingresses
won't necessarily respect this bc by design their controllers usually watchEndpoints
directly to determine what pods are healthy, etc. for routing.https://stackoverflow.com/a/63402311 suggests if controllers leverage
EndpointSlices
instead over time, that they could support topology-aware routing.Without having time to read the code currently, I wanted to clarity on if
EndpointSlices
at all (I saw some issues that referred to them when searching) and therefore does topology-aware routing work ?And 2) if not, is this an enhancement that can be added to the roadmap for v0.16 ?
Thanks for your time/hard work, and looking forward to chatting more on this. Cheers.
The text was updated successfully, but these errors were encountered: