Installation Overview#
At this point, the BCM management plane and rack bring-up are complete — all control plane nodes are provisioned and verified, High Availability is configured, and the GB200/GB300 compute trays are operational. This guide covers the installation of the NVIDIA Mission Control software stack on top of that foundation.
The installation is split into two paths depending on whether your site has confirmed outbound internet access. Most NVIDIA Mission Control deployment sites are air-gapped. If you are unsure, follow the Air-Gap path.
Installation Path Comparison#
The two paths share the same start and end points — prerequisites, Kubernetes installation, and component installation. The air-gap path adds three phases in between to handle artifact download, transfer, and private registry setup before any component is installed.
Phase |
Air-Gap (Recommended) |
Connected |
|---|---|---|
Prerequisites |
✓ |
✓ |
Download NVIDIA Mission Control artifacts ( |
✓ |
— |
Kubernetes Installation |
✓ |
✓ |
Import artifacts into private registry |
✓ |
— |
Configure registry mirroring (containerd / RKE2) |
✓ |
— |
Install NVIDIA Mission Control Components |
✓ |
✓ |
Known limitations |
✓ |
— |
Note
The three air-gap-only phases (download, import, registry mirroring) must be completed before component installation begins. All artifact downloads are performed on an internet-connected machine and transferred to the air-gapped environment as a bundle — no outbound internet access is required from the cluster itself during or after installation.
Choose Your Path#
Follow this path if your deployment site has no confirmed outbound internet access to NGC and all required software repositories — or if you are unsure. This is the recommended path for most NVIDIA Mission Control deployments.
Proceed to NMC Air-Gap Installation.
Follow this path only if your deployment site has confirmed outbound internet access to NGC and all required software repositories.
Proceed to NVIDIA Mission Control Connected Installation.