-
Notifications
You must be signed in to change notification settings - Fork 88
Support endpoint subsetting #415
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
Comments
/assign @LiorLieberman |
In this case, i want to supplement a basic requirement, sometimes gateway instances reside across zone/subzone, so it inference extension should be able to support locality aware routing too. |
@hzxuzhonghu I think that would be a natural extension of this, but not necessarily something that needs to be codified. For example, endpoint extensions could be deployed in each zone. Gateways could then use this protocol to provide zone-local endpoints in the subset that the endpoint extension could pick from. This kind of flexibility would allow the Gateway to provide a broader subset (including endpoints in other zones) if the local zone was overloaded. |
Not implemented yet though. #445 only updated the protocol. I listed this under the next release items: #681 (comment) |
Uh oh!
There was an error while loading. Please reload this page.
What would you like to be added:
Amend the endpoint picker protocol to define how a proxy can limit endpoint picking to a subset of pods.
Why is this needed:
The proxy may not be aligned with epp's view of what pods are ready and what are not. Only the intersection of their views is valid.
The text was updated successfully, but these errors were encountered: