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

[question] [enhancement] EndpointSlices and Topology-Aware Routing #1190

Open
onelapahead opened this issue Dec 12, 2024 · 0 comments
Open

Comments

@onelapahead
Copy link

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

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

@onelapahead onelapahead changed the title [question] EndpointSlices and Topology-Aware Routing [question] [enhancement] EndpointSlices and Topology-Aware Routing Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant