Air-gapped Seed the Registry

Before creating a Kubernetes cluster, you need 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 (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. 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. Set an environment variable with your registry address with 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 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.

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.