-
Notifications
You must be signed in to change notification settings - Fork 178
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
[Bug]: ovms-gpu-ootb is missing recommended accelerator annotation #1991
Comments
@Gkrumbach07 If you would like to include this issue in the 1.34 Release Notes, please provide the text for the "Known issues" section. |
@bredamc here is something The OOTB GPU enabled model serving template is missing the annotation |
Closing this cause we are going to fix it in #1989 |
@andrewballantyne Do you still want to include this bug in the Known issues section of the 1.34 Release Notes? If so, is the following text ok? " When you add a model server to your project, the Serving runtime list does not show the "Recommended serving runtime" label for the NVIDIA GPU. Workaround |
@bredamc Yup that works... it's unfortunate but should be fixed in 1.36 when we release KServe |
Is there an existing issue for this?
Deploy type
OpenDataHub core version (eg.
v1.6.0
)Version
v2.16.0
Current Behavior
the OOTB gpu model serving template is missing the recommended accelerators annotation for
nvidia.com/gpu
so the label does not show up when selecting a NVIDIA GPU.Notes: The OOTB GPU enabled model serving template is missing the annotation
'opendatahub.io/recommended-accelerators': '["nvidia.com/gpu"]'
which makes the "Recommended serving runtime" label not show up in the "Add model server" modal's Serving Runtime dropdown options.Expected Behavior
for the label to show up when selecting the NVIDIA GPU
Steps To Reproduce
nvidia.com/gpu
wont have a recommended label next to itWorkaround (if any)
not a breaking bug, but you can manually add the label when making a copy of the template model server
What browsers are you seeing the problem on?
No response
Anything else
No response
The text was updated successfully, but these errors were encountered: