-
Notifications
You must be signed in to change notification settings - Fork 102
Add subsetting logic for epp #981
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rlakhtakia The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @rlakhtakia. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
envoy specifics should be only in the server.go.
rest of the code should work with go general structs like maps
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a couple comments to future proof us! otherwise lgtm
/retest |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a few nits
// Create a map of endpoint addys for easy lookup | ||
endpoints := make(map[string]bool) | ||
for _, endpoint := range endpointSubsetList { | ||
epStr := strings.Split(endpoint.(string), ":")[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can you add a comment with an example endpoint value and explain why this spitting makes sense?
@@ -86,7 +86,7 @@ func StreamedRequest(t *testing.T, client extProcPb.ExternalProcessor_ProcessCli | |||
return responses, nil | |||
} | |||
|
|||
func GenerateRequest(logger logr.Logger, prompt, model string) *extProcPb.ProcessingRequest { | |||
func GenerateRequest(logger logr.Logger, prompt, model string, filterMetadata interface{}) *extProcPb.ProcessingRequest { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Can we make the filterMetadata
a strongly typed structure for ease of use? Internally in the utils you can do any conversion needed.
"test2", | ||
modelSQLLora, | ||
[]interface{}{"192.168.1.3:8000"}), | ||
// Pod 3 will be picked because it is the only one matching subsetting target. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// Pod 3 will be picked because it is the only one matching subsetting target. | |
// Pod 3 has high queue and kv cache utilization, but it will still be picked because it is the only one matching subsetting target. |
Issue: #415
Proposal
Add subsetting filter to ensure EPP only selects from the list of endpoints passed in through request metadata.
Changes: