Skip to content
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

Feature request: add nvproxy to gVisor if Nvidia driver is included #413

Open
stevefan1999-personal opened this issue Jun 13, 2024 · 1 comment

Comments

@stevefan1999-personal
Copy link

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/

@stevefan1999-personal
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant