Helm Chart Values Reference#
The NVIDIA GPU Operator is installed and configured with a Helm chart. This page is a reference for the most frequently used chart values, grouped by component.
You can set values on the command line with --set <key>=<value> when you install or upgrade the chart, or provide
a values file with -f values.yaml.
To view the complete set of values for a specific chart version, run:
$ helm show values nvidia/gpu-operator --version=v26.7.0
Note
Many chart values populate fields of the ClusterPolicy or GPUCluster custom resources that the chart
creates. For the complete custom resource schemas, refer to the
ClusterPolicy Custom Resource Reference and the
GPUCluster Custom Resource Reference.
Operator and Global Settings#
Parameter |
Description |
Default |
|---|---|---|
|
Map of custom labels to add to all GPU Operator managed pods. |
|
|
List of environment variables ( |
|
|
Map of custom labels to add to all GPU Operator managed DaemonSet pods. |
|
|
Map of custom annotations to add to all GPU Operator managed DaemonSet pods. |
|
|
When set to |
|
|
Deploys |
|
NVIDIA GPU Driver#
These values configure the driver section of ClusterPolicy.
For per-node driver configuration through the NVIDIADriver custom resource, refer to
GPU Driver CRD.
Parameter |
Description |
Default |
|---|---|---|
|
By default, the Operator deploys NVIDIA drivers as a container on the system.
Set this value to |
|
|
When set to |
|
|
Image repository for the driver container. Specify another image repository when using custom driver images. |
|
|
Name of the NVIDIA driver container image to use. |
|
|
Version of the NVIDIA datacenter driver supported by the Operator.
If you set |
Depends on the Operator version. Refer to the GPU Operator Component Matrix. |
|
List of image pull secrets used for pulling the driver container image from the registry. |
None |
|
Type of NVIDIA GPU kernel modules to use. Valid values are |
|
|
Controls whether the driver DaemonSet builds and loads the legacy |
|
|
Indicates that MLNX_OFED (MOFED) drivers are pre-installed on the host. |
|
|
Name of a secret passed to the driver container. A common use is passing an Ubuntu Pro token secret for government-ready components. Refer to NVIDIA GPU Operator Government Ready. |
None |
|
Startup probe configuration for the driver container. By default the probe runs |
|
|
When set to |
|
|
Deprecated as of v25.3.0 and ignored. Use |
|
NVIDIA Container Toolkit#
Parameter |
Description |
Default |
|---|---|---|
|
By default, the Operator deploys the NVIDIA Container Toolkit as a container on the system.
Set this value to |
|
Device Plugin#
Parameter |
Description |
Default |
|---|---|---|
|
Specifies the configuration for the NVIDIA Device Plugin as a config map. In most cases this is configured after installing the Operator, for example to configure Time-Slicing GPUs in Kubernetes. |
|
CDI and NRI#
Parameter |
Description |
Default |
|---|---|---|
|
When set to |
|
|
When set to |
|
|
Deprecated as of v25.10.0 and ignored. |
|
DCGM and DCGM Exporter#
Parameter |
Description |
Default |
|---|---|---|
|
When set to |
|
|
By default, the Operator gathers GPU telemetry using
DCGM Exporter.
Set this value to |
|
|
Specifies the
internalTrafficPolicy
for the DCGM Exporter service. Available values are |
|
|
When set to |
|
|
Map of custom annotations to add to the DCGM Exporter DaemonSet. |
|
|
When set to |
|
|
When set to |
|
|
List of regular expressions that filter which pod labels are emitted as Prometheus dimensions when
|
None |
MIG (Multi-Instance GPU)#
Parameter |
Description |
Default |
|---|---|---|
|
Controls the strategy used with MIG on supported NVIDIA GPUs. Options are |
|
|
The MIG Manager watches for changes to the MIG geometry and applies reconfiguration as needed. By default it only runs on nodes with GPUs that support MIG. |
|
Node Feature Discovery#
Parameter |
Description |
Default |
|---|---|---|
|
Deploys the Node Feature Discovery (NFD) plugin as a DaemonSet.
Set this value to |
|
|
Installs node feature rules related to confidential computing. NFD uses the rules to detect security features
in CPUs and NVIDIA GPUs. Set this value to |
|
DRA Support (GPUCluster)#
These values enable and configure the DRA GPU resource management model.
The gpuCluster.* values populate the GPUCluster custom resource; for the full field list, refer to the
GPUCluster Custom Resource Reference and
Deploying the GPU Operator with DRA Support.
Parameter |
Description |
Default |
|---|---|---|
|
When set to |
|
|
Configures the DRA driver image and its GPU allocation ( |
See reference |
|
Set to |
unset |
Sandbox Workloads#
These values apply when running virtual machine workloads (KubeVirt) or Kata Containers.
Parameter |
Description |
Default |
|---|---|---|
|
Specifies whether sandbox workloads are enabled. |
|
|
Default workload type for the cluster: |
|
|
Sandbox mode used when deploying sandbox workloads. Accepted values are |
|
Other Components#
Parameter |
Description |
Default |
|---|---|---|
|
When set to |
|
|
Enables support for GDRCopy. When set to |
|