Inferensys

Glossary

GPU Operator

A Kubernetes operator that automates the lifecycle management of NVIDIA GPU software components, including drivers, the CUDA toolkit, and monitoring agents, within a containerized cluster.
Developer demonstrating multi-agent tool use, agent tool selection interface on laptop, casual tech demo moment.
KUBERNETES AUTOMATION

What is GPU Operator?

The GPU Operator is a Kubernetes operator that automates the lifecycle management of NVIDIA GPU software components within containerized clusters.

The GPU Operator is a Kubernetes operator that automates the provisioning and lifecycle management of NVIDIA software components—including GPU drivers, the CUDA toolkit, and monitoring agents like DCGM—on worker nodes. It uses the NVIDIA Container Toolkit to expose GPUs to containers, eliminating manual driver installation and ensuring version consistency across the cluster.

By deploying a node feature discovery component to label GPU hardware and a driver container managed via a DaemonSet, the operator reduces operational complexity for platform engineers. It supports GPU time-slicing, Multi-Instance GPU (MIG) partitioning, and integrates with NCCL for optimized multi-node communication, making it essential for managing on-premises GPU clusters at scale.

AUTOMATION COMPONENTS

Key Features of a GPU Operator

A GPU Operator encapsulates the operational knowledge required to manage NVIDIA GPU hardware in Kubernetes, automating the full lifecycle of software components that would otherwise require manual intervention by cluster administrators.

01

Automated Driver Lifecycle Management

The operator manages the complete lifecycle of NVIDIA GPU drivers as Kubernetes DaemonSets, ensuring every GPU node runs a compatible, validated driver version. It handles initial deployment, rolling updates, and node-specific configurations without manual SSH intervention.

  • Precompiled Driver Containers: Ships drivers as OCI-compliant container images, eliminating dependency on the host OS package manager.
  • Node Selector Targeting: Automatically deploys drivers only to nodes with NVIDIA hardware, detected via PCI device labels.
  • Rolling Update Strategy: Orchestrates node cordoning and draining to update drivers without disrupting running GPU workloads.
< 1 min
Driver Deployment per Node
02

Container Runtime & Toolkit Integration

The operator configures the NVIDIA Container Toolkit and the container runtime (e.g., containerd, CRI-O) to expose GPUs to containers. It injects the nvidia-container-runtime as a prestart hook, enabling device node and library mounting.

  • RuntimeClass Registration: Creates a nvidia RuntimeClass in Kubernetes, allowing pods to request GPU resources via runtimeClassName: nvidia.
  • CDI (Container Device Interface): Modern versions use CDI to declaratively define which device nodes, libraries, and binaries are injected into containers.
  • Multi-Runtime Support: Simultaneously configures multiple runtimes (Docker, containerd, CRI-O) on the same node for migration scenarios.
03

GPU Feature Discovery & Node Labeling

The operator deploys GPU Feature Discovery (GFD) to automatically detect and advertise GPU properties as Kubernetes node labels. This enables intelligent scheduling based on hardware capabilities without manual node annotation.

  • Labels Discovered: nvidia.com/gpu.product, nvidia.com/gpu.memory, nvidia.com/gpu.family, nvidia.com/cuda.driver-version.
  • MIG Discovery: Detects Multi-Instance GPU partitioning configurations and exposes available MIG slices as schedulable resources.
  • Dynamic Updates: Labels are refreshed on a configurable interval to reflect hardware changes or driver updates.
04

Monitoring & Telemetry Stack

The operator deploys NVIDIA DCGM Exporter to expose GPU metrics in Prometheus format, integrating with the cluster's existing observability stack. This provides real-time visibility into GPU utilization, temperature, power draw, and error conditions.

  • Metrics Exposed: GPU utilization, memory usage, temperature, power consumption, ECC errors, PCIe throughput, and NVLink bandwidth.
  • XID Error Detection: Captures and exposes NVIDIA XID errors that indicate hardware faults, enabling automated alerting.
  • Grafana Dashboards: Ships with pre-built dashboards for visualizing GPU health across the entire cluster.
100+
GPU Metrics Exposed
05

MIG Partitioning & Configuration

The operator automates the configuration of Multi-Instance GPU (MIG) partitioning on supported NVIDIA data center GPUs (A100, H100, B200). It applies declarative MIG configurations, carving a single physical GPU into isolated, right-sized instances.

  • Declarative MIG Profiles: Define MIG geometry via Kubernetes custom resources, specifying slice counts and sizes (e.g., 1g.5gb, 2g.10gb).
  • Reboot Persistence: MIG configurations survive node reboots, applied automatically by the operator on node startup.
  • Dynamic Reconfiguration: Supports changing MIG partitions on idle GPUs without manual nvidia-smi commands.
06

Validation & Health Checks

The operator includes a GPU Operator Validator component that runs a suite of smoke tests to verify the entire GPU software stack is functioning correctly after deployment. This catches misconfigurations before production workloads are scheduled.

  • CUDA Validation: Runs a simple CUDA kernel to confirm the compiler, driver, and device are communicating.
  • Peer-to-Peer Test: Validates NVLink and GPUDirect P2P connectivity between GPUs on the same node.
  • RDMA Verification: Tests GPUDirect RDMA over InfiniBand or RoCE fabrics for multi-node communication readiness.
GPU OPERATOR

Frequently Asked Questions

Essential questions and answers about the NVIDIA GPU Operator, the Kubernetes-native automation framework for managing the complete lifecycle of GPU software components in containerized environments.

The GPU Operator is a Kubernetes operator developed by NVIDIA that automates the deployment, configuration, and lifecycle management of all NVIDIA GPU software components required to expose and utilize GPUs within a containerized cluster. It functions as a Helm chart that deploys a set of controllers and daemonsets, using the Kubernetes operator pattern to reconcile desired state with actual state. The operator manages the NVIDIA driver container, the container runtime toolkit (nvidia-container-toolkit), the Kubernetes device plugin (nvidia-device-plugin), DCGM monitoring exporters, and the GPU Feature Discovery labeler. When a new GPU node joins the cluster, the operator automatically detects the hardware, installs the appropriate driver version, configures the container runtime to expose GPU devices, and registers the node's GPU resources with the Kubernetes scheduler. This eliminates manual driver installation, version mismatches, and configuration drift across heterogeneous GPU fleets.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.