Installing DevOps Loop in an air-gapped environment

After preparing the required images, plugins, and JDBC drivers in your air-gapped registry or offline storage, you can begin installing DevOps Loop in an air-gapped environment by using Helm.

You must have completed the following tasks:
  • Preloaded images and resources. See preparing_images_resources_air_gapped_installation.html.
  • Ensured that you have administrative privileges on the Kubernetes namespace where DevOps Loop will be installed.
  • Installed and configured Helm on your system.
  • Gained access to the airgap image containing the preloaded images.
  1. Modify the ADDIITIONAL_HELM_OPTIONS variable in the DevOps Loop installation script, to set the following Helm values to point to your airgap registry: 
    --set global.imageRegistry=registry.local:5000/devops-loop 
--set global.externalImageRegistry=registry.local:5000/devops-loop
  2. Edit the DevOps Loop installation script to use the locally downloaded and expanded DevOps Loop Helm chart.
    For OpenShift (OCP) installations, no further changes to the installation script are required.
    For Kubernetes (K8s) installations, you must locate the helm upgrade --install command at the end of the installation script and replace ibm-helm/ibm-devops-loop with ibm-devops-loop.
  3. Follow the DevOps Loop installation instructions based on your environment.
You have installed DevOps Loop in the air-gapped environment.

Before installing additional plug-ins, ensure the required images are available in your internal or air-gapped environment:

  • If you want to install Measure plug-in images that are not included in the standard DevOps Loop set, download them from their public repositories (such as docker.io or hclrc.io) and upload them to your internal or air-gapped image registry.
  • If you want to install Deploy plug-ins that are not included in the standard set, download them from their public repositories to local storage, then upload them to the DevOps Deploy server.