-
Notifications
You must be signed in to change notification settings - Fork 591
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
Support EndpointSlice #1172
Comments
Closing as stale, if anyone is still in need of this support please feel free to comment here with your use cases and we'll be happy to re-open and re-assess. |
Does that mean that Kong still does not support EndpointSlice? |
That's correct today, but this being closed does not mean it's dead it just means it's not an active priority at this very moment. It will be our intention to open this again (or possibly create a new issue) when this becomes a technical blocker or requirement, or sooner if there's a strong need expressed by end-users. |
Reopening this as an overly aggressive stale close. We had clear interest in this based on the earlier PRs and comments here, and got another from @pgold30 with new info as of 1.22, where this is more of a requirement with the endpoint cap. Discussed in Kong/kong#10616Originally posted by pgold30 April 5, 2023 Envoy is designed for scale and the use case for endpointslice also. The lack of EndpointSlices implementation is unfortunately impacting production for us now. Since Kubernetes v1.22, Services that exceed 1000 Pods/network endpoints, Endpoints are now being truncated to a maximum of 1000 items. Outlining the pieces needed to implement this issue @arkodg pointed envoyproxy/gateway#35 (comment) [Relevant Links:] |
Superseded by #3916 |
In Kubernetes 1.21 (release notes, KEP),
EndpointSlice
graduated to GA (GV:discovery.k8s.io/v1
), as a replacement forcore/v1
Endpoint
.This means that KIC can use the following APIs to watch service endpoints:
core/v1
Endpoint
: all versions, with limitations, likely deprecated in the futurediscovery.k8s.io/v1beta1
: k8s 1.18-1.24 (in 1.17 behind a feature gate)discovery.k8s.io/v1
: k8s 1.21+The text was updated successfully, but these errors were encountered: