Support endpoint subsetting

[ahg-g]

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.

[ahg-g]

/assign @LiorLieberman

[hzxuzhonghu]

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.

[robscott]

@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.

[danehans]

@ahg-g can this issue be closed now that #445 merged?

[ahg-g]

Not implemented yet though. #445 only updated the protocol. I listed this under the next release items: #681 (comment)

[liu-cong]

@LiorLieberman

This issue is currently in the v0.4 release tracker and v0.4 release is planned for Mid-June. Can you provide an estimate if this can be finished in the week of June 9?

Based on the estimate, we can decide whether to include this or postpone it to the v0.5 release. Thanks!

[ahg-g]

/assign @rlakhtakia

[k8s-ci-robot]

@ahg-g: GitHub didn't allow me to assign the following users: rlakhtakia.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @rlakhtakia

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[LiorLieberman]

This issue is currently in the v0.4 release tracker and v0.4 release is planned for Mid-June. Can you provide an estimate if this can be finished in the week of June 9?

I am not actively working on it, apologies for not providing the update here