Air-Gapped Deployment

Overview

DPS is a standard Kubernetes application. Deploying it in an air-gapped environment requires that two artifacts are available inside the environment:

Container images – all DPS images must be available in a container registry that the cluster can pull from.
Helm chart – the DPS Helm chart package (.tgz) must be accessible to helm install.

This page does not cover general Kubernetes air-gap procedures such as setting up a private registry or mirroring images. Refer to your Kubernetes distribution’s documentation for those topics.

Standalone Kubernetes

Use standard Helm workflows to prepare the chart and images on a connected machine, then transfer them to the air-gapped environment:

# On a connected machine
helm repo add ngc https://helm.ngc.nvidia.com/nvidia
helm repo update ngc
helm pull ngc/dps                # downloads dps-<version>.tgz

Transfer the .tgz file and all required container images to the air-gapped environment.

Refer to the Deployment Guide for the full set of configuration options.

NVIDIA Mission Control / Base Command Manager

If you are deploying DPS through NVIDIA Mission Control (NMC) or Base Command Manager (BCM), follow the NMC/BCM air-gap packaging documentation to prepare your environment.

Place the DPS Helm chart archive in the following directory on the head node if it is not already there:

/cm/local/apps/dps/var/charts/

The cm-setup installer will automatically detect the local chart and use it instead of pulling from the NGC repository. No additional configuration is required.