feat: add support for custom NVIDIA GPU device selection and capabilities (#161)

* Add support for custom NVIDIA GPU device selection and capabilities

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

* docs: add NVIDIA GPU configuration options to README

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.

* docs: update pms.nvidia values description

---------

Signed-off-by: Gaston Festari <[email protected]>
Co-authored-by: Gaston Festari <[email protected]>

Author: izphi78

charts/plex-media-server/Chart.yaml

@@ -22,7 +22,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.2.0
+version: 1.3.0
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/plex-media-server/README.md

@@ -1,6 +1,6 @@
 # plex-media-server
 
-![Version: 1.2.0](https://img.shields.io/badge/Version-1.2.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.42.2](https://img.shields.io/badge/AppVersion-1.42.2-informational?style=flat-square)
+![Version: 1.3.0](https://img.shields.io/badge/Version-1.3.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 1.42.2](https://img.shields.io/badge/AppVersion-1.42.2-informational?style=flat-square)
 
 **Homepage:** <https://www.plex.tv>
 
@@ -129,6 +129,8 @@ Before contributing, please read the [Code of Conduct](../../CODE_OF_CONDUCT.md)
 | pms.claimSecret.name | string | `""` |  |
 | pms.configExistingClaim | string | `""` | Name of an existing `PersistentVolumeClaim` for the PMS database NOTE: When set, 'configStorage' and 'storageClassName' are ignored. |
 | pms.configStorage | string | `"2Gi"` | The volume size to provision for the PMS database |
+| pms.gpu.nvidia.capabilities | string | `"compute,video,utility"` | Optional: NVIDIA driver capabilities. Available values are: `compute`, `compat32`, `graphics`, `utility`, `video`, `display`. See [NVIDIA docs](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#driver-capabilities) |
+| pms.gpu.nvidia.devices | string | `"all"` | Optional: NVIDIA GPU devices by index or UUID. Examples: "0,1", "GPU-uuid1,GPU-uuid2", or "all". See [NVIDIA docs](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#gpu-enumeration) |
 | pms.gpu.nvidia.enabled | bool | `false` |  |
 | pms.livenessProbe | object | `{}` | Add kubernetes liveness probe to pms container. |
 | pms.readinessProbe | object | `{}` | Add kubernetes readiness probe to pms container. |

charts/plex-media-server/templates/statefulset.yaml

@@ -139,9 +139,9 @@ spec:
         {{- end }}
         {{- if .Values.pms.gpu.nvidia.enabled }}
         - name: NVIDIA_VISIBLE_DEVICES
-          value: all
+          value: {{ .Values.pms.gpu.nvidia.devices | default "all" | quote }}
         - name: NVIDIA_DRIVER_CAPABILITIES
-          value: compute,video,utility
+          value: {{ .Values.pms.gpu.nvidia.capabilities | default "compute,video,utility" | quote }}
         {{- end }}
         {{- with .Values.pms.livenessProbe }}
         livenessProbe:

charts/plex-media-server/values.yaml

@@ -68,6 +68,14 @@ pms:
   gpu:
     nvidia:
       enabled: false
+      # -- Optional: NVIDIA GPU devices by index or UUID.
+      # Examples: "0,1", "GPU-uuid1,GPU-uuid2", or "all".
+      # See [NVIDIA docs](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#gpu-enumeration)
+      devices: "all"
+      # -- Optional: NVIDIA driver capabilities.
+      # Available values are: `compute`, `compat32`, `graphics`, `utility`, `video`, `display`.
+      # See [NVIDIA docs](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html#driver-capabilities)
+      capabilities: "compute,video,utility"
 
   resources: {}
   # We usually recommend not to specify default resources and to leave this as a conscious