-
Notifications
You must be signed in to change notification settings - Fork 405
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
EndpointSlice Support #1256
Comments
Thanks for raising it @pgold30, I will take this in v0.5.0. |
thanks for picking this one up @Xunzhuo ! |
sidenote - this might also require an |
moving this into the backlog for now, since this is not a must have for v0.5.0 |
* Reconcile relavant EndpointSlices associated with a Service that is referenced in a xRoute * Add the EndpointSlices to the provider message Relates to envoyproxy#1256 Signed-off-by: Arko Dasgupta <[email protected]>
* Use common `processRouteDestinations` functions for all xRoute * Precursor to envoyproxy#1256 Signed-off-by: Arko Dasgupta <[email protected]>
* Allows the user to configure a global load balancing strategy for the envoy proxy data plane ``` apiVersion: config.gateway.envoyproxy.io/v1alpha1 kind: EnvoyProxy metadata: name: set-lb-strategy spec: traffic: loadBalancer: strategy: LeastRequest ``` * Sets the default load balancing strategy to `LeastRequest` which will internally set the `WeightedLeastReqquest` knob in Envoy * Relates to envoyproxy#1256 allowing the user to fall back to `ClusterIP` style loadbalancing * Relates to envoyproxy#1105 Signed-off-by: Arko Dasgupta <[email protected]>
* Support EndpointSlice in Kubernetes Provider * Reconcile relavant EndpointSlices associated with a Service that is referenced in a xRoute * Add the EndpointSlices to the provider message Relates to #1256 Signed-off-by: Arko Dasgupta <[email protected]> * race Signed-off-by: Arko Dasgupta <[email protected]> * test Signed-off-by: Arko Dasgupta <[email protected]> --------- Signed-off-by: Arko Dasgupta <[email protected]>
* Cleanup Gateway API Route Destination Logic * Use common `processRouteDestinations` functions for all xRoute * Precursor to #1256 Signed-off-by: Arko Dasgupta <[email protected]>
Relates to envoyproxy#1256 Signed-off-by: Arko Dasgupta <[email protected]>
Hey @arkodg, since you have started working on this issue, let me transfer this to you, thanks! |
Relates to envoyproxy#1256 Signed-off-by: Arko Dasgupta <[email protected]>
Relates to envoyproxy#1256 Signed-off-by: Arko Dasgupta <[email protected]>
* EndpointSlice to IR Route Destinations Relates to #1256 Signed-off-by: Arko Dasgupta <[email protected]> * assign backend weight to locality weight add another level of indirection in RouteDestination called DestinationSetting Signed-off-by: Arko Dasgupta <[email protected]>
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:
[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
The text was updated successfully, but these errors were encountered: