Installation of DevOps Loop in an air-gapped environment
An air-gapped environment is a network or system isolated from the public internet, typically for security or compliance reasons. In such environments, all external resources must be imported manually. DevOps Loop supports air-gapped installations by providing scripts and configurations to transfer required resources into your private environment.
Some deployments operate without internet access, requiring all container images, plugins, and dependencies to be preloaded into a private registry.
Scripts and configurations for Air-gapped installation
airgap.sh script along with Helm configuration parameters to
support air-gapped setups.| Parameter | Description | Example value |
|---|---|---|
global.imageRegistry |
Private registry for product images | registry.local:5000/devops-loop |
global.externalImageRegistry |
Private registry for unqualified/public images. The
airgap.sh script places qualified and
unqualified images in the same image repository, you can
spearate them if required. |
registry.local:5000/public |
airgap.sh |
Script to list or copy required images to private registry | ./airgap.sh -| |
Following are the functions of airgap.sh script:
-
List all the container images required by DevOps Loop (using
-loption). -
Copy images from public registries to your private registry.
