ClusterPolicy Custom Resource Reference#
The ClusterPolicy custom resource definition (CRD) is the primary configuration object for the NVIDIA GPU Operator.
A single ClusterPolicy instance in the cluster describes the desired state of every GPU Operator component—which operands to enable,
which container images to use, and how each component should be configured.
The GPU Operator watches the ClusterPolicy object and reconciles all managed DaemonSets and Deployments to match the desired state.
Note
The NVIDIA GPU Operator also provides a separate NVIDIADriver custom resource for fine-grained, per-node driver configuration.
When you enable the NVIDIA Driver CRD (spec.driver.useNvidiaDriverCRD: true), driver configuration is taken from NVIDIADriver objects rather than from the driver section of ClusterPolicy.
For more information, refer to GPU Driver CRD.
ClusterPolicy Resource Structure#
ClusterPolicy is a cluster-scoped resource in the nvidia.com/v1 API group.
apiVersion: nvidia.com/v1
kind: ClusterPolicy
metadata:
name: gpu-cluster-policy
spec:
operator: {}
daemonsets: {}
driver: {}
toolkit: {}
devicePlugin: {}
dcgmExporter: {}
dcgm: {}
nodeStatusExporter: {}
gfd: {}
mig: {}
migManager: {}
validator: {}
gds: {}
gdrcopy: {}
sandboxWorkloads: {}
vfioManager: {}
sandboxDevicePlugin: {}
vgpuManager: {}
vgpuDeviceManager: {}
cdi: {}
kataManager: {}
ccManager: {}
hostPaths: {}
kataSandboxDevicePlugin: {}
Top-Level Spec Fields
Field |
Description |
Required |
|---|---|---|
|
Configuration options for the GPU Operator itself. |
Yes |
|
Common settings applied to all DaemonSets managed by the Operator. |
Yes |
|
Configuration for deploying and managing the NVIDIA GPU Driver. |
Yes |
|
Configuration for the NVIDIA Container Toolkit. |
Yes |
|
Configuration for the NVIDIA Kubernetes Device Plugin. |
Yes |
|
Configuration for the NVIDIA DCGM Exporter (GPU telemetry). |
Yes |
|
Configuration for deploying NVIDIA DCGM host engine as a standalone pod. |
Yes |
|
Configuration for the Node Status Exporter. |
Yes |
|
Configuration for the NVIDIA GPU Feature Discovery (GFD) plugin. |
Yes |
|
MIG (Multi-Instance GPU) strategy configuration. |
No |
|
Configuration for the NVIDIA MIG Manager. |
No |
|
Configuration for the NVIDIA GPU Operator Validator. |
No |
|
Configuration for NVIDIA GPUDirect Storage (GDS). Experimental. |
No |
|
Configuration for the NVIDIA GDRCopy driver. |
No |
|
Configuration for sandbox workloads (KubeVirt, Kata Containers). |
No |
|
Configuration for the VFIO-PCI Manager (used with VM passthrough workloads). |
No |
|
Configuration for the NVIDIA KubeVirt GPU Device Plugin. |
No |
|
Configuration for the NVIDIA vGPU Manager. |
No |
|
Configuration for the NVIDIA vGPU Device Manager. |
No |
|
Configuration for the Container Device Interface (CDI). |
No |
|
Configuration for the Kata Manager (Kata Containers support). |
No |
|
Configuration for the NVIDIA Confidential Computing Manager. |
No |
|
Custom host filesystem paths used by GPU Operator components. |
No |
|
Configuration for the NVIDIA Kata Sandbox Device Plugin. |
No |
|
Configuration for PodSecurityAdmission. |
No |
|
Deprecated. PodSecurityPolicy configuration (no longer supported). |
No |
Common Component Fields
Most component sections share the following fields. Component-specific fields are documented in each section below.
Field |
Description |
Default |
|---|---|---|
|
Whether the Operator deploys this component.
Set to |
Varies by component. See individual sections. |
|
Container registry and path for the component image. Override this when using a private registry or air-gapped environment. |
Component-specific NGC registry path. |
|
Container image name (without tag). |
Component-specific. |
|
Image tag or version string. |
Defined by the Operator release. Refer to the GPU Operator Component Matrix. |
|
Kubernetes image pull policy.
Accepted values: |
|
|
List of Kubernetes Secret names that contain credentials for pulling images from a private registry. |
None |
|
CPU and memory resource requests and limits for component pods.
Follows the standard Kubernetes |
None (uses Kubernetes defaults) |
|
Additional command-line arguments to pass to the component container. |
None |
|
List of environment variables ( |
None |
|
When |
|
spec.operator#
Configures operator-level settings.
Field |
Description |
Default |
|---|---|---|
|
Specifies the Kubernetes RuntimeClass used for GPU-enabled pods. |
|
|
Map of additional labels to add to all GPU Operator managed pods. |
None |
|
Map of additional annotations to add to all GPU Operator managed pods. |
None |
|
On OpenShift, when set to |
|
|
Deprecated. The container runtime is now detected automatically at runtime. |
N/A |
|
Deprecated. Configuration for the init container image used with all components. |
N/A |
spec.daemonsets#
Applies common settings to all DaemonSets managed by the GPU Operator. These settings serve as defaults and can be supplemented by per-component configuration.
Field |
Description |
Default |
|---|---|---|
|
Map of additional labels to apply to all GPU Operator DaemonSet pods. |
None |
|
Map of additional annotations to apply to all GPU Operator DaemonSet pods. |
None |
|
List of Kubernetes tolerations to apply to all DaemonSet pods. Refer to the Kubernetes tolerations documentation. |
None |
|
Priority class for all DaemonSet pods. |
None |
|
DaemonSet update strategy. Accepted values: |
|
|
For |
|
|
Pod-level security context applied as defaults to all DaemonSet pods.
Follows the standard Kubernetes |
None |
spec.driver#
Controls NVIDIA GPU Driver deployment.
When useNvidiaDriverCRD is false (the default), the Operator manages a single driver DaemonSet
for the entire cluster based on this configuration.
When useNvidiaDriverCRD is true, driver configuration is instead sourced from NVIDIADriver custom resources.
Refer to GPU Driver CRD for details.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
When |
|
|
When |
|
|
Specifies the GPU kernel module type. Accepted values:
|
|
|
Deprecated as of v25.3.0. Use |
N/A |
|
Registry path for the driver container. |
|
|
Driver container image name. |
|
|
GPU driver version to install.
For a standard driver, specify the full version such as |
Version defined by the Operator release. |
|
Image pull policy for the driver container. |
|
|
Image pull secrets for the driver container registry. |
None |
|
When |
|
|
Name of a Kubernetes Secret containing environment variables to pass to the driver container. A common use case is providing an Ubuntu Pro token for government-ready deployments. Refer to NVIDIA GPU Operator Government Ready. |
None |
|
Startup probe settings for the driver container.
By default, the driver container waits 60 seconds before probing with |
|
|
Liveness probe settings for the driver container. See ContainerProbeSpec fields. |
None |
|
Readiness probe settings for the driver container. See ContainerProbeSpec fields. |
None |
|
When |
|
|
When |
|
|
Automatic driver upgrade policy.
When configured, the Operator can perform rolling upgrades of driver pods without manual intervention.
Follows the |
None (upgrades must be triggered manually) |
|
Configuration for the NVIDIA Driver Manager init container, which prepares nodes for driver installation. See DriverManagerSpec fields. |
Managed by the Operator. |
|
Resource requests and limits for the driver container. |
None |
|
Additional arguments for the driver container. |
None |
|
Environment variables for the driver container. |
None |
|
Custom apt/yum repository configuration for the driver container. Specify a ConfigMap name that the Operator mounts into the driver container for custom package sources. Refer to Install NVIDIA GPU Operator in Air-Gapped Environments for air-gapped use cases. |
None |
|
Custom certificate configuration for the driver container. Specify a ConfigMap name containing custom CA certificates. |
None |
|
vGPU license configuration. See DriverLicensingConfigSpec fields. Required when deploying with NVIDIA vGPU. |
None |
|
Virtual topology daemon configuration for NVIDIA vGPU drivers.
Specify a ConfigMap name containing the |
None |
|
Custom kernel module parameters for the NVIDIA driver. Specify a ConfigMap name containing kernel module configuration. Refer to Customizing NVIDIA GPU Driver Parameters during Installation. |
None |
ContainerProbeSpec Fields#
Used by startupProbe, livenessProbe, and readinessProbe in the driver section.
Field |
Description |
Default |
|---|---|---|
|
Seconds to wait after the container starts before initiating probes. |
|
|
Seconds after which a probe times out. Minimum value: |
|
|
How often (in seconds) to perform the probe. Minimum value: |
|
|
Minimum consecutive successes for the probe to be considered successful. Minimum: |
|
|
Minimum consecutive failures before the probe is considered failed. Minimum: |
|
DriverManagerSpec Fields#
Configures the Driver Manager init container that runs before the driver container to manage driver lifecycle (for example, unloading existing modules before an upgrade).
Field |
Description |
Default |
|---|---|---|
|
Registry path for the Driver Manager image. |
Operator default. |
|
Driver Manager image name. |
|
|
Driver Manager image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy for the Driver Manager image. |
|
|
Image pull secrets for the Driver Manager registry. |
None |
|
Environment variables to set in the Driver Manager init container. |
None |
DriverLicensingConfigSpec Fields#
Required for NVIDIA vGPU deployments to configure the license server.
Field |
Description |
Default |
|---|---|---|
|
Name of a Kubernetes Secret containing the NLS (NVIDIA Licensing System) client configuration token. Refer to Using NVIDIA vGPU. |
None |
|
Deprecated. Use |
None |
|
When |
|
spec.toolkit#
Controls deployment of the NVIDIA Container Toolkit, which configures the container runtime (containerd, CRI-O, or Docker) to support GPU-accelerated containers.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the Container Toolkit image. |
|
|
Container Toolkit image name. |
|
|
Container Toolkit image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
Host path where the NVIDIA Container Toolkit installs its binaries. |
|
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments for the Container Toolkit container. |
None |
|
Environment variables for the Container Toolkit container. Used to configure non-default container runtime socket paths or configuration locations. Refer to Installing the NVIDIA GPU Operator for examples. |
None |
spec.devicePlugin#
Controls deployment of the NVIDIA Kubernetes Device Plugin, which advertises GPU resources to the Kubernetes scheduler. For configuration options such as time-slicing, MPS, or MIG strategy, the Device Plugin is configured through a ConfigMap. Refer to Time-Slicing GPUs in Kubernetes and GPU Operator with MIG.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the Device Plugin image. |
|
|
Device Plugin image name. |
|
|
Device Plugin image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments for the Device Plugin container. |
None |
|
Environment variables for the Device Plugin container. |
None |
|
Name of the ConfigMap containing the Device Plugin configuration. The ConfigMap can contain multiple named configurations for different node types. Refer to Time-Slicing GPUs in Kubernetes for configuring time-slicing and MPS. |
None |
|
The default configuration name within the ConfigMap to use when no specific configuration is selected. |
None |
|
Host path to use as the MPS (Multi-Process Service) root directory. Relevant when using the Device Plugin in MPS mode. |
|
spec.dcgmExporter#
Controls deployment of the NVIDIA DCGM Exporter, which exposes GPU metrics in Prometheus format. Refer to the DCGM Exporter documentation for details on available metrics.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the DCGM Exporter image. |
|
|
DCGM Exporter image name. |
|
|
DCGM Exporter image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments for the DCGM Exporter container. |
None |
|
Environment variables for the DCGM Exporter container. |
None |
|
Name of the ConfigMap containing a custom |
None (uses default metric set) |
|
Kubernetes Service type for the DCGM Exporter Service. Refer to the Kubernetes Service documentation. |
|
|
Internal traffic policy for the DCGM Exporter Service.
Use |
|
|
When |
|
|
How frequently Prometheus scrapes DCGM Exporter.
If not specified, Prometheus uses its global scrape interval.
Supported units: |
Prometheus global scrape interval |
|
When |
|
|
Map of additional labels to add to the |
None |
|
List of Prometheus relabel configurations to rewrite labels on metric sets.
Follows the Prometheus Operator |
None |
|
When |
|
|
Host directory path where HPC job mapping files are written by the workload manager. |
|
spec.dcgm#
Controls deployment of NVIDIA DCGM host engine as a standalone pod. By default, DCGM runs as a sidecar in the DCGM Exporter pod. Enabling the standalone DCGM pod can improve performance when multiple consumers need to connect to the same DCGM host engine.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the DCGM image. |
|
|
DCGM image name. |
|
|
DCGM image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Deprecated. Host port previously used for the DCGM engine. |
N/A |
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.nodeStatusExporter#
Controls deployment of the Node Status Exporter, which reports GPU node status information to the Kubernetes API.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the Node Status Exporter image. |
|
|
Node Status Exporter image name. |
|
|
Image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.gfd#
Controls deployment of the NVIDIA GPU Feature Discovery (GFD) plugin, which labels Kubernetes nodes with GPU hardware properties (such as GPU model, driver version, CUDA version, and MIG configuration). Node Feature Discovery (NFD) must be deployed in the cluster for GFD to function.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the GFD image. |
|
|
GFD image name. |
|
|
GFD image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.mig#
Configures the MIG (Multi-Instance GPU) strategy. Refer to GPU Operator with MIG for complete MIG configuration guidance.
Field |
Description |
Default |
|---|---|---|
|
MIG strategy to use on MIG-capable GPUs (such as A100, H100). Accepted values:
|
|
spec.migManager#
Controls deployment of the NVIDIA MIG Manager, which watches for MIG geometry changes and automatically reconfigures nodes. The MIG Manager runs only on MIG-capable nodes.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the MIG Manager image. |
|
|
MIG Manager image name. |
|
|
MIG Manager image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
|
Name of the ConfigMap containing the |
None |
|
Default MIG configuration to apply when a node has no |
|
|
Name of the ConfigMap listing GPU client processes that the MIG Manager should stop before reconfiguring MIG geometry. |
None |
spec.validator#
Controls deployment of the NVIDIA GPU Operator Validator, which runs a series of tests to confirm that each GPU Operator component is functioning correctly on each node. The Validator runs as a DaemonSet and reports pass/fail status.
Field |
Description |
Default |
|---|---|---|
|
Registry path for the Validator image. |
|
|
Validator image name. |
|
|
Validator image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
|
Environment variables specific to the Device Plugin validation step. |
None |
|
Environment variables specific to the Container Toolkit validation step. |
None |
|
Environment variables specific to the driver validation step. |
None |
|
Environment variables specific to the CUDA workload validation step. |
None |
|
Environment variables specific to the VFIO-PCI device validation step. |
None |
|
Environment variables specific to the vGPU Manager validation step. |
None |
|
Environment variables specific to the vGPU device validation step. |
None |
spec.gds#
Controls deployment of the NVIDIA GPUDirect Storage (GDS) driver. GDS enables direct DMA transfers between GPU memory and storage without CPU involvement. This feature is experimental.
When using the NVIDIADriver CRD, configure GDS within the NVIDIADriver spec instead.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the GDS driver image. |
|
|
GDS driver image name. |
|
|
GDS driver image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.gdrcopy#
Controls deployment of the NVIDIA GDRCopy driver (gdrdrv kernel module), which enables
low-latency GPU-to-CPU memory copies using GPUDirect RDMA.
When using ClusterPolicy-managed drivers, the GDRCopy driver runs as a sidecar in the driver pod.
When using the NVIDIADriver CRD, configure GDRCopy within the NVIDIADriver spec instead.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the GDRCopy driver image. |
|
|
GDRCopy driver image name. |
|
|
GDRCopy driver image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.sandboxWorkloads#
Controls support for sandbox-based GPU workloads such as KubeVirt virtual machines or Kata Containers. When enabled, the Operator deploys additional components including the VFIO Manager, vGPU Manager (if applicable), and sandbox-specific device plugins.
Refer to GPU Operator with KubeVirt and Deploy with Kata Containers for deployment guides.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Default GPU workload type to configure on worker nodes. Accepted values:
|
|
|
Sandbox mode for sandboxed workloads. Accepted values:
|
|
spec.vfioManager#
Controls deployment of the VFIO-PCI Manager, which binds GPU devices to the vfio-pci
kernel driver to enable PCI passthrough to virtual machines.
Only deployed when sandboxWorkloads.enabled is true and sandboxWorkloads.mode is kubevirt.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the VFIO Manager image. |
|
|
VFIO Manager image name. |
|
|
VFIO Manager image version. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
|
Driver Manager configuration for the VFIO Manager. See DriverManagerSpec fields. |
Managed by the Operator. |
spec.sandboxDevicePlugin#
Controls deployment of the NVIDIA KubeVirt GPU Device Plugin, which advertises vGPU and GPU passthrough
devices to the Kubernetes scheduler for use by KubeVirt virtual machines.
Only deployed when sandboxWorkloads.enabled is true.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the Sandbox Device Plugin image. |
|
|
Sandbox Device Plugin image name. |
|
|
Image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.vgpuManager#
Controls deployment of the NVIDIA vGPU Manager (vGPU host driver), which runs on the hypervisor node
and manages vGPU instances for virtual machines.
Only deployed when sandboxWorkloads.enabled is true.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the vGPU Manager image. |
Must be specified; images are not on NGC. |
|
vGPU Manager image name. |
Must be specified. |
|
vGPU Manager image version. Must match the NVIDIA vGPU software version in use. |
Must be specified. |
|
Image pull policy. |
|
|
Image pull secrets. Required if images are on a private registry. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
|
Custom kernel module parameters for the vGPU Manager. |
None |
|
Driver Manager configuration. See DriverManagerSpec fields. |
Managed by the Operator. |
spec.vgpuDeviceManager#
Controls deployment of the NVIDIA vGPU Device Manager, which manages vGPU device creation on virtualization hosts.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the vGPU Device Manager image. |
|
|
vGPU Device Manager image name. |
|
|
vGPU Device Manager image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
|
Name of the ConfigMap containing the vGPU device configuration. The ConfigMap can contain multiple named configurations. |
None |
|
Default configuration name within the ConfigMap. |
|
spec.cdi#
Configures how the Container Device Interface (CDI) is used in the cluster. CDI is the default and recommended mechanism for exposing GPU devices to containers. Refer to Container Device Interface (CDI) and Node Resource Interface (NRI) Plugin Support for more information.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
When |
|
|
Deprecated as of v25.10.0. CDI is enabled by default and this field is ignored. |
N/A |
spec.kataManager#
Controls deployment of the NVIDIA Kata Manager, which prepares NVIDIA-specific Kata runtime classes
on nodes for use with Kata Containers-based sandbox workloads.
Only deployed when sandboxWorkloads.enabled is true and sandboxWorkloads.mode is kata.
Refer to Deploy with Kata Containers for deployment guidance.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Kata Manager configuration specifying which kata runtime artifacts to use.
Follows the |
None |
|
Registry path for the Kata Manager image. |
|
|
Kata Manager image name. |
|
|
Kata Manager image version. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.ccManager#
Controls deployment of the NVIDIA Confidential Computing Manager, which configures the Confidential Computing (CC) mode on compatible GPUs (H100 and later).
Refer to Confidential Containers for deployment guidance.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Default Confidential Computing mode to apply to all CC-capable GPUs on each node. Accepted values:
|
None |
|
Registry path for the CC Manager image. |
|
|
CC Manager image name. |
|
|
CC Manager image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.kataSandboxDevicePlugin#
Controls deployment of the NVIDIA Kata Sandbox Device Plugin, which advertises GPU devices
to the Kubernetes scheduler for use with Kata Containers-based sandbox workloads.
Deployed when sandboxWorkloads.enabled is true and sandboxWorkloads.mode is kata.
Field |
Description |
Default |
|---|---|---|
|
When |
|
|
Registry path for the Kata Sandbox Device Plugin image. |
|
|
Kata Sandbox Device Plugin image name. |
|
|
Image version. Refer to the GPU Operator Component Matrix. |
Version defined by the Operator release. |
|
Image pull policy. |
|
|
Image pull secrets. |
None |
|
When |
|
|
Resource requests and limits. |
None |
|
Additional arguments. |
None |
|
Environment variables. |
None |
spec.hostPaths#
Defines custom host filesystem paths needed by GPU Operator components. Override these only when your nodes use non-standard filesystem layouts.
Field |
Description |
Default |
|---|---|---|
|
Path to the root filesystem of the host. Must be a chroot-able filesystem. Used by components that interact with the host OS directly (for example, MIG Manager and Container Toolkit when stopping or restarting systemd services). |
|
|
Root directory where the GPU driver files (libraries, executables, configuration) are installed. Override when using a custom driver install path. |
|
spec.psa#
Configures PodSecurityAdmission for GPU Operator pods.
Field |
Description |
Default |
|---|---|---|
|
When |
|
ClusterPolicy Status Fields#
The Operator sets the following fields in ClusterPolicy.status.
Field |
Description |
Values |
|---|---|---|
|
Overall state of the ClusterPolicy. |
|
|
Namespace in which the GPU Operator is installed. |
Operator namespace string. |
|
List of Kubernetes conditions describing the detailed state of the ClusterPolicy.
Each condition has a |
Standard Kubernetes condition list. |
To check the ClusterPolicy status:
$ kubectl get clusterpolicy gpu-cluster-policy -o jsonpath='{.status}'