NMC Launchpad (air-gapped)

In an air-gapped environment, NMC Launchpad and its dependencies are installed using Helm charts from the bundle artifacts instead of pulling from remote registries. All other configuration steps — including values file preparation, Keycloak setup, and post-install verification — remain the same as the standard installation. Refer to the following guides for the complete instructions:

• NMC Launchpad installation guide

• Keycloak installation guide

Note

The ngcImageCredentials section in values-launchpad.yaml is not required in an air-gapped environment because container images are already available in the local registry. You can remove or leave the ngcImageCredentials block empty. No changes to image repository paths are needed — registry mirroring redirects image pulls to the local registry automatically.

Install Components

Use the bundle artifacts to install each component. The values files referenced in the following commands are the same ones described in the standard installation guide.

helm install cnpg ./bundle/helm/cloudnative-pg-0.27.0.tgz \
  --namespace launchpad --create-namespace -f values-cnpg-operator.yaml

helm install keycloak-cnpg ./bundle/helm/cluster-0.5.0.tgz \
  --namespace launchpad -f values-cnpg-cluster.yaml

helm install keycloakx ./bundle/helm/keycloakx-7.1.7.tgz \
  --namespace launchpad -f values-keycloakx.yaml

helm install keycloak-config-cli ./bundle/helm/keycloak-config-cli-1.3.4.tgz \
  --namespace launchpad -f values-keycloak-config-cli.yaml

helm install nmc-launchpad ./bundle/helm/nmc-launchpad-0.2.13.tgz \
  --namespace launchpad -f values-launchpad.yaml

After installation, continue with the verification steps in the verification section.