Create a local mirror

After you prepare an offline copy of artifacts as described in Prepare an offline copy for an air-gapped cluster, proceed to create and configure a local mirror that is a demo CDN for testing purposes and for transferring an offline copy to a private CDN. For more details about demo CDN, see Demo CDN storage size.

Prepare a demo CDN

  1. Log in to the node where the offline copy is supposed to be located.

  2. Make sure that the offline copy content is availabe in the AIRGAPPED_WORKSPACE directory by either mounting the offline copy volume to the AIRGAPPED_WORKSPACE mount point, or copying its entire content to AIRGAPPED_WORKSPACE.

  3. Change the directory to <AIRGAPPED_WORKSPACE>/kaas-bootstrap.

  4. Make sure that the AIRGAPPED_WORKSPACE variable in airgapped.env matches your airgapped workspace path.

  5. Export the variables from airgapped.env to the current shell. The make-artifacts-list.py script and the commands below read AIRGAPPED_WORKSPACE from the environment:

    set -a; source ./airgapped.env; set +a
    
  6. Import the helper Docker images:

    ./docker-load.sh
    
  7. Export the required files and images. For example:

    ./airgapped.sh export \
    --kaas-release kaas-2-32-0 \
    --cluster-release k0s-22-0-0-1-33-13 \
    --cluster-release mosk-21-2-0-26-2
    

    Example of system response extract:

    ...
    2026-11-16 15:18:49 [INFO   ] Exporting files ... Reading cache
    2026-11-16 15:18:58 [INFO   ] Exporting filesystem layout ...
    2026-11-16 15:19:02 [INFO   ] Exporting filesystem layout - done.
    2026-11-16 15:19:02 [INFO   ] Exporting files - OK. Total files - 45748, failed files - 0.
    2026-11-16 15:19:02 [INFO   ] Exporting images ... Reading cache
    2026-11-16 15:19:02 [INFO   ] Exporting images to OCI layout ...
    2026-11-16 15:19:03 [INFO   ] Exporting images to OCI layout - done.
    2026-11-16 15:19:03 [INFO   ] Exporting images - OK. Total images - 262, failed images - 0.
    
  8. Re-generate the release index file:

    ./airgapped.sh make-release-index
    

    Example of system response extract:

    ...
    2026-11-16 15:19:04 [INFO   ] Generating index.yaml ...
    2026-11-16 15:19:06 [INFO   ] '/workspace/files/by-name/binary.mirantis.com/releases/index.yaml' generated successfully.
    
  9. Initialize the demo CDN services:

    ./airgapped.sh demo --init --san-ip <DEMO_CDN_IP>
    

    DEMO_CDN_IP is an IP address of a system where you run the demo CDN Docker services. It can be either the host IP address of a physical node or a floating IP address of an OpenStack instance.

    Warning

    Run the demo --init command only once as it creates a CA certificate each time unconditionally. Previously created .crt / .key files will be backed up, but backup keeps only one most recent version of each file.

    The CA certificate named demo-ca.crt is saved in the ${AIRGAPPED_WORKSPACE}/shared/ directory and is available by the http://<DEMO_CDN_IP>:8080/demo-ca.crt link.

  10. Add the demo CA certificate to the trusted certificates of the node. Otherwise, airgapped.sh validate fails to verify the demo CDN over HTTPS with the CERTIFICATE_VERIFY_FAILED error:

    sudo cp "${AIRGAPPED_WORKSPACE}/shared/demo-ca.crt" /usr/local/share/ca-certificates/demo-ca.crt
    sudo update-ca-certificates
    
  11. Start the demo CDN services:

    ./airgapped.sh demo up -d
    
  12. Push Docker images. For example:

    ./airgapped.sh push \
    --kaas-release kaas-2-32-0 \
    --cluster-release k0s-22-0-0-1-33-13 \
    --cluster-release mosk-21-2-0-26-2 \
    --url-map="registry=<DEMO_CDN_IP>" \
    --insecure-registry
    

    Example of system response extract:

    ...
    2026-11-16 15:56:55 [INFO   ] Pushing images to remote registry ...
    2026-11-16 16:03:08 [INFO   ] Pushing images done (passed / failed): 262 / 0
    
  13. Validate the demo CDN. For example:

    ./airgapped.sh validate \
    --kaas-release kaas-2-32-0 \
    --cluster-release k0s-22-0-0-1-33-13 \
    --cluster-release mosk-21-2-0-26-2 \
    --url-map "binary=https://<DEMO_CDN_IP>:8081" \
    --url-map "debian=https://<DEMO_CDN_IP>:8082" \
    --url-map "mcr-repo=https://<DEMO_CDN_IP>:8083" \
    --url-map "registry=<DEMO_CDN_IP>"
    

    Example of system response extract:

    ...
    2026-11-16 16:03:09 [INFO   ] Validating files ...
    2026-11-16 16:03:09 [INFO   ] Validating remote files ... Total files: 45748, running 112 workers.
    2026-11-16 16:10:14 [INFO   ] Validating remote files - OK. Total files: 45748, bad files - 0.
    2026-11-16 16:10:14 [INFO   ] Validating files - OK.
    2026-11-16 16:10:14 [INFO   ] Validating images ...
    2026-11-16 16:10:14 [INFO   ] Validating remote images ... Total images 262, running 30 threads.
    2026-11-16 16:10:15 [INFO   ] Validating remote images - OK. Total images - 262, failed images - 0, errors - 0
    2026-11-16 16:10:15 [INFO   ] Validating images - OK.
    

    If some artifacts are missing:

    1. Add missing artifacts:

      • For Docker images, run airgapped.sh push

      • For files, run airgapped.sh export --files --no-images

    2. Repeat the demo CDN validation.

Transfer artifacts from the demo CDN to private CDN

  1. Copy validated artifacts from the demo CDN to the private CDN by keeping the directory structure under each CDN intact. Use your preferred tool, for example, skopeo, curl, rsync, or JFrog CLI.

    If you need complete lists of files and images available on each type of demo CDN, use the previously prepared make-artifacts-list.py script to generate these lists:

    ./make-artifacts-list.py
    

    The lists of files and images are available in the following locations:

    • binary resource files –> http://<DEMO_CDN_IP>:8080/binary_files.txt

    • debian resource files –> http://<DEMO_CDN_IP>:8080/debian_repo_files.txt

    • mcr-repo resource files –> http://<DEMO_CDN_IP>:8080/mcr_repo_files.txt

    • registry resource images –> http://<DEMO_CDN_IP>:8080/docker_images.txt

    Caution

    To keep these lists synchronized with the demo CDN content, run make-artifacts-list.py each time after the airgapped.sh export command.

  2. Mandatory. Validate the artifacts in the private CDN after transferring.

    If the private CDN uses a certificate signed by a CA that this node does not trust, register the CA certificate on the node in the same way as the demo CA certificate. Otherwise, airgapped.sh validate fails with the CERTIFICATE_VERIFY_FAILED error.

    For example:

    ./airgapped.sh validate \
    --kaas-release kaas-2-32-0 \
    --cluster-release k0s-22-0-0-1-33-13 \
    --cluster-release mosk-21-2-0-26-2 \
    --url-map "binary=<MCC_CDN_BINARY>" \
    --url-map "debian=<MCC_CDN_DEBIAN>" \
    --url-map "mcr-repo=<MCC_CDN_MCR_REPO>" \
    --url-map "registry=<MCC_CDN_DOCKER>"
    

    Example of system response extract:

    ...
    2026-11-16 16:03:09 [INFO   ] Validating files ...
    2026-11-16 16:03:09 [INFO   ] Validating remote files ... Total files: 45748, running 112 workers.
    2026-11-16 16:10:14 [INFO   ] Validating remote files - OK. Total files: 45748, bad files - 0.
    2026-11-16 16:10:14 [INFO   ] Validating files - OK.
    2026-11-16 16:10:14 [INFO   ] Validating images ...
    2026-11-16 16:10:14 [INFO   ] Validating remote images ... Total images 262, running 30 threads.
    2026-11-16 16:10:15 [INFO   ] Validating remote images - OK. Total images - 262, failed images - 0, errors - 0
    2026-11-16 16:10:15 [INFO   ] Validating images - OK.
    

    If some artifacts are missing in the offline copy:

    1. Re-run make-artifacts-list.py to update the artifacts list.

    2. Repeat the artifacts transferring steps.

    3. Repeat the artifacts validation.

Proceed to Deploy an air-gapped management cluster.