Inferensys

Glossary

GPU Operator

A Kubernetes operator that automates the deployment and lifecycle management of all software components required to expose and monitor GPUs in a cluster.
ML engineer managing model training cluster on laptop, GPU utilization visible, technical deep learning setup.
KUBERNETES GPU AUTOMATION

What is a GPU Operator?

A GPU Operator is a Kubernetes-native controller that automates the complete lifecycle management of software components required to provision, monitor, and maintain GPU hardware in a cluster.

A GPU Operator is a Kubernetes operator, most commonly the NVIDIA GPU Operator, that automates the deployment and lifecycle management of all software components required to expose and monitor GPUs in a cluster. It manages the entire GPU software stack—including drivers, the container runtime, device plugins, and monitoring frameworks—reducing the operational complexity of managing heterogeneous accelerator hardware at scale.

The operator leverages Custom Resource Definitions (CRDs) to declaratively define the desired state of GPU software. It automates the installation and configuration of node-specific components like kernel drivers and the NVIDIA Container Toolkit, ensuring every GPU node in the cluster is consistently provisioned. This is critical for air-gapped and disconnected Kubernetes environments, where manual driver installation is error-prone and the operator can manage pre-staged, offline-compatible software bundles.

AUTOMATED LIFECYCLE MANAGEMENT

Key Features of the GPU Operator

The GPU Operator automates the deployment and lifecycle management of all software components required to expose and monitor GPUs in a Kubernetes cluster, eliminating manual driver installation and configuration drift.

01

Automated Driver Deployment

Manages the entire lifecycle of NVIDIA GPU drivers as Kubernetes DaemonSets. The operator detects the GPU hardware on each node and automatically deploys the correct, validated driver version.

  • Eliminates manual driver installation on bare-metal hosts
  • Ensures driver consistency across the entire cluster
  • Supports pre-compiled, pre-validated driver containers for air-gapped environments
< 5 min
Node provisioning time
02

Container Runtime & Toolkit Integration

Deploys the NVIDIA Container Toolkit and configures the container runtime (containerd or CRI-O) to expose GPUs to containers. This includes the nvidia-container-runtime hook and the nvidia-container-toolkit binary.

  • Configures the OCI runtime spec to mount GPU device nodes
  • Enables the nvidia.com/gpu resource type in Kubernetes
  • Manages the libnvidia-container library stack for GPU enumeration
03

GPU Monitoring & Telemetry

Deploys the NVIDIA Data Center GPU Manager (DCGM) and the DCGM Exporter to expose GPU metrics to Prometheus. Provides deep hardware telemetry for operational visibility.

  • Exposes metrics: GPU utilization, memory usage, temperature, power draw, ECC errors
  • Integrates with the Prometheus Operator via ServiceMonitor CRDs
  • Enables GPU-specific Horizontal Pod Autoscaler (HPA) rules based on DCGM metrics
04

GPU Feature Discovery & Labeling

Uses the GPU Feature Discovery (GFD) component to automatically label nodes with their GPU properties. This enables intelligent scheduling based on hardware capabilities.

  • Labels: nvidia.com/gpu.product, nvidia.com/gpu.count, nvidia.com/gpu.memory
  • Enables node affinity and node selector rules for specific GPU models
  • Supports NVIDIA MIG (Multi-Instance GPU) partitioning discovery and labeling
05

Operator Lifecycle & Validation

Manages its own lifecycle through a ClusterPolicy Custom Resource Definition (CRD). The ClusterPolicy is the single declarative configuration point for the entire GPU software stack.

  • Validates component versions and driver-container compatibility
  • Supports air-gapped deployments via private container registries
  • Integrates with the Node Feature Discovery (NFD) operator for hardware enumeration
06

MIG Configuration & Management

Automates the configuration of Multi-Instance GPU (MIG) partitioning on supported NVIDIA data center GPUs (A100, H100). The operator can declaratively define MIG geometry.

  • Defines MIG profiles via the ClusterPolicy CRD
  • Creates isolated GPU instances with dedicated memory and compute slices
  • Enables fine-grained GPU sharing for inference workloads without virtualization overhead
GPU OPERATOR

Frequently Asked Questions

Essential questions about automating GPU provisioning and lifecycle management in Kubernetes clusters, with a focus on disconnected and air-gapped environments.

A GPU Operator is a Kubernetes-native controller, most commonly the NVIDIA GPU Operator, that automates the entire lifecycle of GPU software components required to expose and monitor accelerators in a cluster. It functions as a meta-operator, deploying and managing a set of underlying components as a unified stack. The operator uses a Custom Resource Definition (CRD) to define a declarative ClusterPolicy object. When applied, the operator's reconciliation loop installs and configures the necessary NVIDIA driver container, the container runtime plugin (nvidia-container-toolkit), the Kubernetes device plugin (nvidia-device-plugin), and the Data Center GPU Manager (DCGM) for monitoring. This eliminates the manual, error-prone process of installing kernel drivers, ensuring version compatibility, and configuring the container runtime on every node. In disconnected environments, the operator's Helm Chart can be pre-packaged with all dependent container images and driver binaries, enabling a fully automated GPU provisioning workflow without internet access.

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.