-
Notifications
You must be signed in to change notification settings - Fork 207
Rename part two #1968
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?
Rename part two #1968
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: shmuelk 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 |
a468127 to
a592084
Compare
Signed-off-by: Shmuel Kallner <[email protected]>
Signed-off-by: Shmuel Kallner <[email protected]>
Signed-off-by: Shmuel Kallner <[email protected]>
Signed-off-by: Shmuel Kallner <[email protected]>
a592084 to
0d81658
Compare
|
PR needs rebase. 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. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR is a second PR in a set of PRs that is attempting to cleanup the code base WRT to Pods vs Model Server Endpoints.
It does this in two ways:
As Model Servers evolve, vLLM or others, one can not assume that there is a one to one relationship between pods and Model Servers. That is a pod may contain multiple Model Servers each. on its own port, such as vLLM's Data Parallel support. On the other hand Model Servers may do there own internal multi-pod routing as well.
Does this PR introduce a user-facing change?: