-
Notifications
You must be signed in to change notification settings - Fork 55
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
Adding printer columns to inference model #574
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kfswain The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
api/v1alpha2/inferencemodel_types.go
Outdated
@@ -25,6 +25,10 @@ import ( | |||
// +kubebuilder:object:root=true | |||
// +kubebuilder:subresource:status | |||
// +kubebuilder:storageversion | |||
// +kubebuilder:printcolumn:name="Model Name", type=string,JSONPath=`.spec.modelName` | |||
// +kubebuilder:printcolumn:name="Inference Pool", type=string,JSONPath=`.spec.poolRef.name` |
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.
Criticality is operationally important
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.
I looked into adding it, but it's optional, so I thought that might be odd to have some empty entries.
For posterity/context: We specifically made this field optional so it could be nullable, should we ever make a replacement field we could retroactively one-of them.
That being said, we can still add it, as I agree, it is important.
Also inference model please (the referent) |
targetModels is an array, which is also optional. So just to talk this out (which is kinda why I omitted), what behavior do we want? Is a count sufficient and then the user describes the model they want to look into further? That could be useful as: LMKWYT |
/lgtm |
The target model thing seems like a bug, I designed custom printers to support arrays, but something may have changed since then. |
You might need to use “range” in the target model column. |
Fixes: #504