Install Overview#
The NVIDIA GPU Operator supports many Kubernetes platforms, licensing models, and deployment configurations. This page helps you choose the install guide that matches your environment. Each linked page contains the step-by-step procedures; start here when you are not sure where to begin.
Before you install, review Prerequisites to confirm that your cluster, hardware, and tooling meet the requirements for your chosen path.
Red Hat OpenShift Container Platform
If you run Red Hat OpenShift, install the GPU Operator through OperatorHub or the OpenShift CLI (OLM), not the Helm quickstart in this book. Refer to NVIDIA GPU Operator on Red Hat OpenShift Container Platform for OpenShift install, upgrade, and disconnected deployment procedures.
GPU Resource Management#
The GPU Operator supports managing GPU resources on your cluster using the following methods:
NVIDIA Device Plugin through the
ClusterPolicycustom resource.DRA Driver for NVIDIA GPUs through the
GPUClustercustom resource.
At install time, choose one GPU resource management model for the cluster.
Use either ClusterPolicy or GPUCluster; using both in the same cluster is not supported.
Note
Deploying the DRA model through the GPUCluster custom resource is in Technology Preview and is supported only
for greenfield (new) deployments.
The GPUCluster API is served under nvidia.com/v1alpha1 and is subject to change in future releases.
Migrating an existing ClusterPolicy deployment to GPUCluster in place is not supported.
Component |
Device-plugin model ( |
DRA model ( |
|---|---|---|
GPU allocation |
NVIDIA Kubernetes Device Plugin (extended resources) |
DRA Driver for NVIDIA GPUs (ResourceClaims) |
NVIDIA GPU driver |
Managed by |
Pre-installed or managed by |
Default install path |
Do not deploy ClusterPolicy and GPUCluster as GPU resource management models in the same cluster.
Refer to Deploying the GPU Operator with DRA Support for the supported greenfield DRA
deployment.
For the fully supported standalone DRA Driver Helm chart (without Operator-managed GPUCluster), refer to
DRA Driver for NVIDIA GPUs.
Driver Provisioning#
How the NVIDIA GPU driver is installed is independent of which platform or GPU resource management model you choose.
Model |
When to use |
Where to configure |
|---|---|---|
Operator-managed ( |
Default for generic Kubernetes and most cloud installs |
|
|
Per-node or mixed-OS driver management; use this for Operator-managed drivers with the DRA model |
|
Pre-installed on the host |
Driver already present on GPU nodes ( |
Install with Helm, Microsoft AKS, or Deploying the GPU Operator with DRA Support |
NVIDIA Licenses#
If your deployment requires a licensed NVIDIA product or a sovereign-cloud configuration, use one of these guides instead of the default Helm install.
Install with NVAIE licensing using the NGC Bash script (vGPU guest) or standard Helm (datacenter driver).
Build a custom driver image and install with vGPU licensing secrets.
Deploy STIG- and FIPS-hardened containers for sovereign and FedRAMP environments. Requires NVAIE licensing.
Platform#
Select the guide for your Kubernetes distribution or cloud platform.
Install with Helm on upstream Kubernetes, bare-metal hosts, or VMs with GPU passthrough. This is the default path for most self-managed clusters.
Prepare Ubuntu node groups and choose between the default EKS GPU stack and Operator-managed drivers.
Compare AKS GPU options and install the Operator with --skip-gpu-driver-install or pre-installed drivers.
Choose between the Google driver installer plus the Operator, or full Operator driver management on Ubuntu nodes.
Install through OperatorHub or oc using the OpenShift documentation book.
Validated configurations for partner Kubernetes distributions such as Mirantis MKE and SUSE RKE2.
Deploy on Anthos clusters on bare metal or VMware vSphere.
Specialized Network Environments#
These guides apply in addition to your primary install path when the cluster has network or mesh constraints.
Configure the driver container to reach external endpoints through a proxy.
Mirror images and package repositories for disconnected clusters.
Disable sidecar injection on the gpu-operator namespace before installing.
Suggested Paths#
If you are new to the GPU Operator, follow one of these common sequences.
Common journeys:
Bare metal or generic Kubernetes: Prerequisites → Install with Helm → verify
Amazon EKS, Azure AKS, or Google GKE: Prerequisites → platform guide → Install with Helm → verify
Red Hat OpenShift: NVIDIA GPU Operator on Red Hat OpenShift Container Platform (OperatorHub or
ocinstall)DRA-native cluster (Technology Preview): Prerequisites → Deploying the GPU Operator with DRA Support → verify
If your cluster uses a restricted network, add the matching guide from Specialized Network Environments before or during install.
Next Steps#
After you choose a path:
Review Prerequisites for your platform, license, and GPU resource management model.
Follow the install guide for your chosen path.
Verify the installation using the steps in that guide.
Configure workloads (MIG, time-slicing, RDMA, and others) from the Advanced Operator Configuration section in the sidebar.