If you are operating in an air-gapped environment, a local container registry containing all the necessary installation images, including the Kommander images is required. See below for how to push the necessary images to this registry.
Download the Complete DKP Air-gapped Bundle for this release (i.e.
Connectivity with clusters attaching to the management cluster:
Both management and attached clusters must be able to connect to the local 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 attached cluster.
Note: You can also attach clusters when there are networking restrictions between the management cluster and attached cluster.
See Attach a Cluster with Networking Restrictions for more information.
Extract Air-gapped Images and Set Variables
Follow these steps to extract the air-gapped image bundles into your private registry:
Assuming you have downloaded
dkp-air-gapped-bundle_v2.6.0_linux_amd64.tar.gz, extract the tarball to a local directory:CODE
tar -xzvf dkp-air-gapped-bundle_v2.6.0_linux_amd64.tar.gz && cd dkp-v2.6.0
Set an environment variable with your registry address:CODE
export REGISTRY_ADDRESS=<registry-address>:<registry-port> export REGISTRY_USERNAME=<username> export REGISTRY_PASSWORD=<password>
Load Images to your Private Registry - Kommander
Load Kommander images to your Private Registry
For the air-gapped
kommander image bundle, run the command below:
Run the following command to load the image bundle:
dkp push bundle --bundle ./container-images/kommander-image-bundle-v2.6.0.tar --to-registry $REGISTRY_ADDRESS
Load Images to your Private Registry - DKP Catalog Applications
Optional: This step is required only if you have an Enterprise license.
For DKP Catalog Applications, also perform this image load:
Run the following command to load the
dkp-catalog-applications image bundle into your private registry:
dkp push bundle --bundle ./container-images/dkp-catalog-applications-image-bundle-v2.6.0.tar --to-registry $REGISTRY_ADDRESS
Load Images to your Private Registry - Konvoy
Before creating or upgrading a Kubernetes cluster, you need to load the required images in a local registry if operating in an air-gapped environment. This registry must be accessible from both the bastion machine and either the AWS EC2 instances or other machines that will be created for the Kubernetes cluster.
If you do not already have a local registry set up, refer to Local Registry Tools page for more information.
Execute the following command to load the air-gapped image bundle into your private registry:
dkp push bundle --bundle ./container-images/konvoy-image-bundle-v2.6.0.tar --to-registry $REGISTRY_ADDRESS --to-registry-username $REGISTRY_USERNAME --to-registry-password $REGISTRY_PASSWORD
It may take some time 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.