You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We also ran into this issue with Kubeflow Pipelines on k3s. You can implement a mutating admission controller to apply on-the-fly custom modifications (such as adding a runtimeClassName field) to resource creation requests
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Feature Area
In my GPU cluster to make a K8s pod able to use GPU is to specify spec.runtimeClassName: nvidia .
(https://kubernetes.io/docs/concepts/containers/runtime-class/#usage)
What feature would you like to see?
Ability to add RuntimeClass Name into the component or task.
Ex.
What is the use case or pain point?
Able to have a component that able to use GPU (ex. Train Model)
Is there a workaround currently?
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: