-
Notifications
You must be signed in to change notification settings - Fork 88
Rename the PodMetrics type #360
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
I like Let the Great Name Wars commence! 😆 |
Nit: in a multi-node setup, the server is not just a pod, it is a group of pods. While we could say that we only care about the single pod representing the group (aka the leader), an endpoint might be more generic here especially if we name the extension "Endpoint Picker". |
The InferencePoolSpec.Selector documented to select model server pods, so how about |
I generally think this item is lower priority compared to increasing test coverage though. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Perhaps we can name it
Endpoint
The text was updated successfully, but these errors were encountered: