Installing NVIDIA Mission Control Components in Air-Gapped Mode#

Install each NVIDIA Mission Control component in air-gapped mode using the steps for that component:

  • cm-setup wizards: NetQ, AHR, and AJR use the BCM cm-mission-control-setup --skip-packages (or component-specific) wizards. Install the corresponding plugin packages from bundle/files/ on the BCM head node first.

  • Direct Helm install: NMC Gateway, Keycloak, NVIDIA Mission Control Launchpad, and K8s security policy are installed from the local Helm tarball or your OCI Helm repo. Ensure values point at your air-gap registry or local resources.

NMC Gateway is the entry point for the Keycloak and NVIDIA Mission Control Launchpad web interfaces. Install it before those components.

The Autonomous Recovery Engine (ARE) consists of two independently installed components: Autonomous Hardware Recovery (AHR) and Autonomous Job Recovery (AJR). Both must be installed to enable full ARE functionality. Install both components after Run:ai, as shown in the following sequence. This ensures that the Run:ai BCM node categories and the k8s-user kubectl context exist when the ARE installation wizards run.

Note

The Helm values files in these steps hold administrator passwords, database passwords, and client secrets in plain text. Store them where only the cluster administrator can read them, or delete them once the component is installed and verified.

Note

Run:ai installs on the k8s-user cluster (k8s-system-user nodes), not the k8s-admin cluster. Ensure the k8s-system-user node category and the GPU worker node category are created in BCM before running the Run:ai installation wizard.

Note

Power Reservation Steering has no air-gap-specific installation steps. Follow the connected installation instructions in Power Reservation Steering for this component.