Install Kommander in an Air-gapped Environment

How to install Kommander using an Air-gapped installation

Depending on your configuration, there are three different ways you can install DKP to an air-gapped environment.
Ensure you follow the correct procedure for your configuration type below:

DKP Essential:

• Install Kommander in an air-gapped environment

• Install air-gapped Kommander with DKP Insights

DKP Enterprise:

• Install air-gapped Kommander with DKP Catalog Applications

• Install air-gapped Kommander with DKP Insights and DKP Catalog Applications

Prerequisites

Before installing, ensure you have:

• A registry containing all the necessary installation images, including the Kommander images. See below for how to push the necessary images to this registry.

• Download the Complete DKP Air-gapped Bundle for this release (i.e. dkp-air-gapped-bundle_v2.5.2_linux_amd64.tar.gz)

• Connectivity with clusters attaching to the management cluster:

  • Both management and attached clusters must be able to connect to the registry.

  • The management cluster must be able to connect to all attached cluster’s API servers.

  • The management cluster must be able to connect to any load balancers created for platform services on the management cluster.

• All the prerequisites covered in air-gapped DKP installation.

• Sufficient resources on your cluster to run Kommander. Review the Management cluster application requirements and Workspace platform application requirements for application requirements.

• A load balancer to route external traffic which is provided by your cloud provider. For on-premises deployments, you must configure MetalLB. See Load Balancing topic for more details.

Load the Images into Your Registry

Follow these steps:

1. Assuming you have downloaded dkp-air-gapped-bundle_v2.5.2_linux_amd64.tar.gz , extract the tarball to a local directory:

   CODE

   tar -xzvf dkp-air-gapped-bundle_v2.5.2_linux_amd64.tar.gz && cd dkp-v2.5.2

2. See the NOTICES.txt file for 3rd party software attributions in the container-images/ directory.

3. Set an environment variable with your registry address:

   CODE

   export REGISTRY_ADDRESS=<registry-address>:<registry-port>

4. Run the following command to load the air-gapped kommander image bundle into your private registry:

   CODE

   dkp push image-bundle --image-bundle ./container-images/kommander-image-bundle-v2.5.2.tar --to-registry $REGISTRY_ADDRESS

5. If you are using DKP catalog applications, run the following command to load the dkp-catalog-applications image bundle into your private registry:

   CODE

   dkp push image-bundle --image-bundle ./container-images/dkp-catalog-applications-image-bundle-v2.5.2.tar --to-registry $REGISTRY_ADDRESS

6. If you are using DKP Insights, run the following command to load the dkp-insights image bundle into your private registry:

   CODE

   dkp push image-bundle --image-bundle ./container-images/dkp-insights-image-bundle-v2.5.2.tar --to-registry $REGISTRY_ADDRESS

It can take a while to push all the images to your image registry, depending on the performance of the network between the machine you are running the script on and the registry.

Next Step

Choose the correct air-gapped environment from the pages in this section.