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
Looks like the situation is a little more complicated. Technically speaking if you have the driver installed on Talos as an extension and configured k8s-device-plugin to use CDI, and then let either NFD discover the GPU or add the specified label forcefully, then k8s-device-plugin should be able to populate CDI manifest and update the node with GPU allocation information, and inject the needed driver into the container during pod creation. Therefore, the following config to the helm chart of k8s-device-plugin should work:
deviceListStrategy: cdi-cri
Then according to google/gvisor#9368 (comment), gVisor should be able to load up the CDI manifest from k8s-device-plugin and inject the devices to the sentry.
But it is not sure whether CDI is going to work in Talos in the first place.
gVisor should have out of the box support for most GPU workload
The guide can be found here: https://gvisor.dev/docs/user_guide/gpu/
The text was updated successfully, but these errors were encountered: