-
Notifications
You must be signed in to change notification settings - Fork 512
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
Allow changes to the NVIDIA device plugin configurations #2347
Comments
+1, since I'd like to use the time-slicing feature. |
+1 same requirement for using time-slicing feature. |
Any ETA for implementation of this feature? |
Hi team, do we have any updates on this? Our workaround now is using AL2 but we would like to leverage the smaller footprint of BottleRocket, thanks! |
Any ETA for this feature? |
Any updates on this ? |
Hi @RamezWasfy , |
Hey @monirul anything we could do to help push this across the line? |
Can we have some clarification on the time-slicing that landed in 1.25? I take it this does not have anything to do with MIG or vGPU. I'm asking because the security guidance mentions that time-slicing is not safe to enable due to concerns around memory safety, etc. I think MIG and vGPU (which are alternative time-slicing strategies) do provide better isolation guarantees. So I'm wondering if those are slated for support as well. Our use case centers around efficiently (but safely) allocating and sharing GPU resources in a multi-tenant environment. Here are some resources:
|
@jcmcken I would open a new issue for MiG since that is separate from time-slicing and requires mig-parted |
What I'd like:
The NVIDIA device plugin allows a user to configure it through a configuration file. NVIDIA variants should allow users to change this configurations, as described in the NVIDIA Device plugin documentation.
Any alternatives you've considered:
Keep status quo, but this should be supported.
The text was updated successfully, but these errors were encountered: