AWS Loading the Registry

Because air-gapped environments do not have direct access to the Internet, you must download, extract and load several required images to your local container registry, before installing DKP. Refer to Registry Mirror Tools for specific information.

Load Images into your Registry

After you create an image for your Air-gapped environment, you will need to load your registry. However, local registries can also be used in Non-air-gapped environments for speed and security reasons. If you choose to use this feature in your Non-air-gapped environment, then this page will apply to you.

Download all Images for Air-gapped Deployments

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 prerequisites to download and then how to push the necessary images to this registry.

1. Download the Complete DKP Air-gapped Bundle for this release (i.e. dkp-air-gapped-bundle_v2.7.1_linux_amd64.tar.gz) to load registry images as explained below.

2. Connectivity with clusters attaching to the management cluster is required:

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

Extract Air-gapped Images and Set Variables

Follow these steps to extract the air-gapped image bundles into your private registry using these examples for ECR:

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

   CODE

   tar -xzvf dkp-air-gapped-bundle_v2.7.0_linux_amd64.tar.gz

2. The directory structure after extraction can be accessed in subsequent steps using commands to access files from different directories. For the bootstrap, change your directory to the dkp-<version> directory similar to example below depending on your current location:

   CODE

   cd dkp-v2.7.0

3. Set an environment variable with your registry address for ECR:

   CODE

   export REGISTRY_URL=<ecr-registry-URI>

NOTE: To use ECR:

• REGISTRY_URL: the address of an existing local registry accessible in the VPC that the new cluster nodes will be configured to use a mirror registry when pulling images.

• The environment where you are running the dkp push command must be authenticated with AWS in order to load your images into ECR.

export REGISTRY_URL="<https/http>://<registry-address>:<registry-port>"
export REGISTRY_USERNAME=<username>
export REGISTRY_PASSWORD=<password>
export REGISTRY_CA=<path to the cacert file on the bastion>

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.7.0.tar --to-registry=${REGISTRY_URL}

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.

For specific push flags, refer to the dkp push bundlesection of CLI commands.

dkp push bundle --bundle ./container-images/konvoy-image-bundle-v2.7.0.tar --to-registry=${REGISTRY_URL} --to-registry-username=${REGISTRY_USERNAME} --to-registry-password=${REGISTRY_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.7.0.tar --to-registry=${REGISTRY_URL}

dkp push bundle --bundle ./container-images/kommander-image-bundle-v2.7.0.tar --to-registry=${REGISTRY_URL} --to-registry-username=${REGISTRY_USERNAME} --to-registry-password=${REGISTRY_PASSWORD}

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.7.0.tar --to-registry=${REGISTRY_URL}

dkp push bundle --bundle ./container-images/dkp-catalog-applications-image-bundle-v2.7.0.tar --to-registry=${REGISTRY_URL} --to-registry-username=${REGISTRY_USERNAME} --to-registry-password=${REGISTRY_PASSWORD}

Related Topic

AWS Elastic Container Registry (ECR)

Next Step

AWS Registry Configuration