About Installing the Operator and NVIDIA vGPU

NVIDIA Virtual GPU (vGPU) enables multiple virtual machines (VMs) to have simultaneous, direct access to a single physical GPU, using the same NVIDIA graphics drivers that are deployed on non-virtualized operating systems.

The GPU Operator can install the

The installation steps assume gpu-operator as the default namespace for installing the NVIDIA GPU Operator. In case of Red Hat OpenShift Container Platform, the default namespace is nvidia-gpu-operator. Change the namespace shown in the commands accordingly based on your cluster configuration. Also replace kubectl in the below commands with oc when running on RedHat OpenShift.

NVIDIA vGPU is only supported with the NVIDIA License System.

Platform Support

For information about the supported platforms, see Supported Deployment Options, Hypervisors, and NVIDIA vGPU Based Products.

For Red Hat OpenShift Virtualization, see NVIDIA GPU Operator with OpenShift Virtualization.


Before installing the GPU Operator on NVIDIA vGPU, ensure the following:

  • The NVIDIA vGPU Host Driver version 12.0 (or later) is pre-installed on all hypervisors hosting NVIDIA vGPU accelerated Kubernetes worker node virtual machines. Refer to NVIDIA Virtual GPU Software Documentation for details.

  • You must have access to the NVIDIA Enterprise Application Hub at and the NVIDIA Licensing Portal.

  • Your organization must have an instance of a Cloud License Service (CLS) or a Delegated License Service (DLS).

  • You must generate and download a client configuration token for your CLS instance or DLS instance. Refer to the NVIDIA License System Quick Start Guide for information about generating a token.

  • You have access to a private registry, such as NVIDIA NGC Private Registry, and can push container images to the registry.

  • Git and Docker or Podman are required to build the vGPU driver image from source repository and push to the private registry.

  • Each Kubernetes worker node in the cluster has access to the private registry. Private registry access is usually managed through image pull secrets. You specify the secrets to the NVIDIA GPU Operator when you install the Operator with Helm.


    Uploading the NVIDIA vGPU driver to a publicly available repository or otherwise publicly sharing the driver is a violation of the NVIDIA vGPU EULA.

Download vGPU Software

Perform the following steps to download the vGPU software and the latest NVIDIA vGPU driver catalog file from the NVIDIA Licensing Portal.

  1. Log in to the NVIDIA Enterprise Application Hub at and then click NVIDIA LICENSING PORTAL.

  2. In the left navigation pane of the NVIDIA Licensing Portal, click SOFTWARE DOWNLOADS.

  3. Locate vGPU Driver Catalog in the table of driver downloads and click Download.

  4. Click the PRODUCT FAMILY menu and select vGPU to filter the downloads to vGPU only.

  5. Locate the vGPU software for your platform in the table of software downloads and click Download.

The vGPU software is packaged as a ZIP file. Unzip the file to obtain the NVIDIA vGPU Linux guest driver. The guest driver file name follows the pattern NVIDIA-Linux-x86_64-<version>

Build the Driver Container

Perform the following steps to build and push a container image that includes the vGPU Linux guest driver.

  1. Clone the driver container repository and change directory into the repository:

    $ git clone
    $ cd driver
  2. Change directory to the operating system name and version under the driver directory:

    $ cd ubuntu20.04

    For Red Hat OpenShift Container Platform, use a directory that includes rhel in the directory name.

  3. Copy the NVIDIA vGPU guest driver from your extracted ZIP file and the NVIDIA vGPU driver catalog file:

    $ cp <local-driver-download-directory>/* drivers/
    $ cp vgpuDriverCatalog.yaml drivers/
  4. Set environment variables for building the driver container image.

    • Specify your private registry URL:

      $ export PRIVATE_REGISTRY=<private-registry-url>
    • Specify the OS_TAG environment variable to identify the guest operating system name and version:

      $ export OS_TAG=ubuntu20.04

      The value must match the guest operating system version. For Red Hat OpenShift Container Platform, specify rhcos4.<x> where x is the supported minor OCP version. Refer to Supported Operating Systems and Kubernetes Platforms for the list of supported OS distributions.

    • Specify the driver container image tag, such as 1.0.0:

      $ export VERSION=1.0.0

      The specified value can be any user-defined value. The value is used to install the Operator in a subsequent step.

    • Specify the version of the CUDA base image to use when building the driver container:

      $ export CUDA_VERSION=11.8.0

      The CUDA version only specifies which base image is used to build the driver container. The version does not have any correlation to the version of CUDA that is associated with or supported by the resulting driver container.

    • Specify the Linux guest vGPU driver version that you downloaded from the NVIDIA Licensing Portal and append -grid:

      $ export VGPU_DRIVER_VERSION=525.60.13-grid

      The Operator automatically selects the compatible guest driver version from the drivers bundled with the driver image. If you disable the version check by specifying --build-arg DISABLE_VGPU_VERSION_CHECK=true when you build the driver image, then the VGPU_DRIVER_VERSION value is used as default.

  5. Build the driver container image:

    $ sudo docker build \
        --build-arg DRIVER_TYPE=vgpu \
        --build-arg CUDA_VERSION=$CUDA_VERSION \
        --build-arg TARGETARCH=amd64 \  # amd64 or arm64
        -t ${PRIVATE_REGISTRY}/driver:${VERSION}-${OS_TAG} .
  6. Push the driver container image to your private registry.

    1. Log in to your private registry:

      $ sudo docker login ${PRIVATE_REGISTRY} --username=<username>

      Enter your password when prompted.

    2. Push the driver container image to your private registry:

      $ sudo docker push ${PRIVATE_REGISTRY}/driver:${VERSION}-${OS_TAG}

Configure the Cluster with the vGPU License Information and the Driver Container Image

  1. Create an NVIDIA vGPU license file named gridd.conf with contents like the following example:

    # Description: Set Feature to be enabled
    # Data type: integer
    # Possible values:
    # 0 => for unlicensed state
    # 1 => for NVIDIA vGPU
    # 2 => for NVIDIA RTX Virtual Workstation
    # 4 => for NVIDIA Virtual Compute Server
  2. Rename the client configuration token file that you downloaded to client_configuration_token.tok using a command like the following example:

    $ cp ~/Downloads/client_configuration_token_03-28-2023-16-16-36.tok client_configuration_token.tok

    The file must be named client_configuraton_token.tok.

  3. Create the gpu-operator namespace:

    $ kubectl create namespace gpu-operator
  4. Create a config map that is named licensing-config using the gridd.conf and client_configuration_token.tok files:

    $ kubectl create configmap licensing-config \
        -n gpu-operator --from-file=gridd.conf --from-file=client_configuration_token.tok
  5. Create an image pull secret in the gpu-operator namespace with the registry secret and private registry.

    1. Set an environment variable with the name of the secret:

      $ export REGISTRY_SECRET_NAME=registry-secret
    2. Create the secret:

      $ kubectl create secret docker-registry ${REGISTRY_SECRET_NAME} \
          --docker-server=${PRIVATE_REGISTRY} --docker-username=<username> \
          --docker-password=<password> \
          --docker-email=<email-id> -n gpu-operator

    You need to specify the secret name REGISTRY_SECRET_NAME when you install the GPU Operator with Helm.

Install the Operator

  • Install the Operator:

    $ helm install --wait --generate-name \
         -n gpu-operator --create-namespace \
         nvidia/gpu-operator \
         --set driver.repository=${PRIVATE_REGISTRY} \
         --set driver.version=${VERSION} \
         --set driver.imagePullSecrets={$REGISTRY_SECRET_NAME} \
         --set driver.licensingConfig.configMapName=licensing-config

The preceding command installs the Operator with the default configuration. Refer to Common Chart Customization Options for information about configuration options.

Next Steps