Pre-provisioned Air-gapped FIPS: Load 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.
Assuming you have downloaded
dkp-air-gapped-bundle_v2.5.0_linux_amd64.tar.gz, extract the tarball to a local directory:CODE
tar -xzvf dkp-air-gapped-bundle_v2.5.0_linux_amd64.tar.gz && cd dkp-v2.5.0
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>
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.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.
To increase Docker Hub's rate limit use your Docker Hub credentials when creating the cluster, by setting the following flag
--registry-mirror-url=https://registry-1.docker.io --registry-mirror-username= --registry-mirror-password= on the
dkp create cluster command.
Kommander Load Images
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.
For the basic air-gapped
kommander image bundle, run the command below:
Run the following command to load the image bundle:CODE
dkp push image-bundle --image-bundle ./container-images/kommander-image-bundle-v2.5.0.tar --to-registry $REGISTRY_ADDRESS
For DKP Catalog Applications, also perform this image load:
Run the following command to load the
dkp-catalog-applicationsimage bundle into your private registry:CODE
dkp push image-bundle --image-bundle ./container-images/dkp-catalog-applications-image-bundle-v2.5.0.tar --to-registry $REGISTRY_ADDRESS