Air-gapped Seed the Registry

Before creating an air-gapped Kubernetes cluster, you need to load the required images in a local registry. This registry must be accessible from both the bastion machine and either the AWS EC2 instances (if deploying to AWS) 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. Download dkp-air-gapped-bundle_v2.6.2_linux_amd64.tar.gz , and extract the tarball to a local directory:

   CODE

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

2. Set an environment variable with your registry address using this command:

   CODE

   export REGISTRY_ADDRESS=<registry-address>:<registry-port>
   export REGISTRY_USERNAME=<username>
   export REGISTRY_PASSWORD=<password>

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

   CODE

   dkp push bundle --bundle ./container-images/konvoy-image-bundle-v2.6.2.tar --to-registry $REGISTRY_ADDRESS --to-registry-username $REGISTRY_USERNAME --to-registry-password $REGISTRY_PASSWORD

   NOTE: To use ECR, set an environment variable with your registry address for ECR:

   CODE

   export REGISTRY_URL=<ecr-registry-URI>

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

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.

You are now ready to create an air-gapped bootstrap cluster for a custom cluster for your infrastructure provider, or create an air-gapped cluster from the Day 1 - Basic Installs section for your provider.