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

Plans for Transitioning to EndpointSlice for Service Discovery #9803

Open
ermakov-oleg opened this issue Jul 23, 2024 · 0 comments · May be fixed by #10290
Open

Plans for Transitioning to EndpointSlice for Service Discovery #9803

ermakov-oleg opened this issue Jul 23, 2024 · 0 comments · May be fixed by #10290

Comments

@ermakov-oleg
Copy link

Do you have a suggestion for code improvement or tracking existing technical debt? Please describe.

Hello Gloo team,

I am wondering if there are any plans for Gloo to transition from using traditional Kubernetes Endpoints to the newer EndpointSlice API for service discovery? The EndpointSlice API offers improved scalability and performance, which could benefit Gloo users, especially in large-scale environments. Additionally, this transition could enable features like Topology Aware Routing in the future.

Thank you for your hard work on Gloo. Any updates or insights on this potential transition would be greatly appreciated.

Describe the solution you'd like

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant