Description:
EndpointSlice is now enabled by default in Kubernetes and offers some solid performance benefits for clusters with large Endpoint sets. It might be worthwhile to support consuming EndpointSlice, at least as optional.

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.
Im sure there are many other people with the same issue. (same here in Countour)

Outlining the pieces needed to implement this issue @arkodg pointed here

Work Items:

• Add EndpointSlice support in the Kubernetes Provider feat: Support EndpointSlice in Kubernetes Provider #1474
• Parse EndpointSlice support to Xds IR Route Destinations in the Gateway API Translator EndpointSlice to IR Route Destinations #1494
• Support routing to Service Cluster IP #1900

[Relevant Links:]
Similar to Countour open issue.
This was shortly discussed here and this explanation
This was fixed on Feb 15 for nginx-ingress here