Upgrade: For Air-gapped Environments Only

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. dkp-air-gapped-bundle_v2.5.2_linux_amd64.tar.gz) to load registry images as explained below.

• 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 management cluster.

• For Pre-provisioned air-gapped environments only, you must run konvoy-image upload artifacts to copy the artifacts onto the cluster hosts before you begin the Upgrade the CAPI Components section below.

  CODE

  konvoy-image upload artifacts \
      --container-images-dir=./artifacts/images/ \
      --os-packages-bundle=./artifacts/$OS_PACKAGES_BUNDLE \
      --containerd-bundle=artifacts/$CONTAINERD_BUNDLE \
      --pip-packages-bundle=./artifacts/pip-packages.tar.gz

Follow these steps to load the air-gapped image bundles into your private registry:

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>
   export REGISTRY_USERNAME=<username>
   export REGISTRY_PASSWORD=<password>

For the basic air-gapped kommander image bundle, run the command below:

1. Run the following command to load the image bundle:

   CODE

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

For DKP Catalog Applications, also perform this image load:

1. 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

If you are running DKP Insights, also perform this image load command:

1. 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

Before creating 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, please refer to Local Registry Tools page for more information.

1. Execute the following command to load the air-gapped image bundle into your private registry:

   CODE

   dkp push image-bundle --image-bundle ./container-images/konvoy-image-bundle-v2.5.2.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.