feat: add support for custom NVIDIA GPU device selection and capabilities#161
Merged
cilindrox merged 7 commits intoplexinc:masterfrom Nov 27, 2025
Merged
Conversation
Allow users to specify custom GPU devices and driver capabilities for NVIDIA GPU workloads instead of using hardcoded defaults. Changes: - Add optional `pms.gpu.nvidia.devices` field (default: "all") Supports GPU indices, UUIDs, or "all" for all GPUs - Add optional `pms.gpu.nvidia.capabilities` field (default: "compute,video,utility") - Add documentation links to NVIDIA Container Toolkit docs - Use Helm default function for cleaner template syntax Users can now specify specific GPUs (e.g., "0,1" or by UUID) and customize driver capabilities (compute, video, utility, graphics, etc.) according to their workload requirements. References: - GPU enumeration: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#gpu-enumeration - Driver capabilities: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#driver-capabilities
Document new configurable fields for NVIDIA GPU support: - pms.gpu.nvidia.devices: GPU device selection - pms.gpu.nvidia.capabilities: Driver capabilities configuration Include links to official NVIDIA Container Toolkit documentation for GPU enumeration and driver capabilities. Bump chart version.
cilindrox
reviewed
Nov 26, 2025
Co-authored-by: Gaston Festari <cilindrox@gmail.com>
Co-authored-by: Gaston Festari <cilindrox@gmail.com>
Co-authored-by: Gaston Festari <cilindrox@gmail.com>
Contributor
Author
|
Thank you for the quick response ! :) Do I need to sign my commits ? If so, shall I open a new PR or force push the new commits ? |
Rename claimSecret.value -> claimSecret.key conditional check in the `statefulset.yaml` template.
Signed-off-by: Gaston Festari <cilindrox@gmail.com>
cilindrox
changed the title
Member
|
This has shipped on v1.3.0 - thanks @izphi78 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow users to specify custom GPU devices and driver capabilities
for NVIDIA GPU workloads instead of using hardcoded defaults.
Changes:
pms.gpu.nvidia.devicesfield (default: "all")Supports GPU indices, UUIDs, or "all" for all GPUs
pms.gpu.nvidia.capabilitiesfield(default: "compute,video,utility")
Users can now specify specific GPUs (e.g., "0,1" or by UUID) and
customize driver capabilities (compute, video, utility, graphics, etc.)
according to their workload requirements.
References: