Installing DevOps Loop on IBM Red Hat OpenShift

You can install IBM® DevOps Loop on an IBM Red Hat OpenShift Container Platform (OCP) cluster to automate DevOps workflows, manage continuous integration and deployment pipelines, and monitor application performance across environments. To simplify the deployment, DevOps Loop provides a Helm-based installation script that automates prerequisite configuration and component installation.

You must have completed the following tasks:
  1. Prepare the cluster environment:
    1. Log in to your OpenShift cluster by using the oc CLI.
    2. Create or select a project (namespace) for the installation.
    3. Ensure that the required storage classes are available (ReadWriteOnce or ReadWriteMany).
    4. Verify that the cluster has internet connectivity if you plan to install DevOps Loop using the online method. Internet access is required to download container images and Helm charts directly from IBM repositories.
    5. Optional: Prepare a certificate secret if you are using CA-signed certificates.
  2. Optional: Configure Sysdig for IBM Cloud-managed OpenShift clusters:

    If you are installing DevOps Loop on an IBM Cloud-managed Red Hat OpenShift cluster, configure Sysdig to prevent RabbitMQ pod restart issues.

    1. Open the Sysdig agent config map:
      oc edit configmap sysdig-agent -n ibm-observe
    2. Add the following filter configuration, in the dragent.yaml section:
      use_container_filter: true
      container_filter:
        - exclude:
            kubernetes.pod.label.app.kubernetes.io/name: rabbitmq
        - exclude:
            kubernetes.pod.label.service: velocity-rabbitmq
    3. Save and exit the editor to apply the change.

      Wait for few minutes for the configuration to take effect.

  3. Configure access to the IBM Entitled Registry:
    1. Retrieve your entitlement key from IBM Container Software Library.
    2. Create an image pull secret in your OpenShift namespace to access IBM container images:
      oc create secret docker-registry ibm-entitlement-key \
        --namespace <namespace> \
        --docker-username=cp \
        --docker-password=<entitlement-key> \
        --docker-server=cp.icr.io
  4. Add the IBM Helm repository and download the DevOps Loop Helm chart:
    helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm --force-update
    helm pull --untar ibm-helm/ibm-devops-loop --version 2.0.200
  5. Configure the following installation parameters:
    • Cluster FQDN (DOMAIN)

    • License acceptance (ACCEPT_LICENSE=true)

    • License server (LICENSE_SERVER)

    • SMTP configuration

    • Password seed

    • TLS certificate settings

    Note: IBM Cloud automatically configures the cluster domain and ingress routing when you set the default domain to the DevOps Automation domain. This ensures that DevOps Loop components are accessible without requiring manual domain or ingress setup.
  6. Run the installation script:
    sh ./ibm-devops-loop/scripts/IBM-loop-OCP-install.sh
    The script automates MongoDB provisioning, Configuration secrets, TLS setup and Helm deployment of DevOps Loop components.
  7. Verify the installation by running the following command:
    oc get pods -n devops-loop
    Note: For more information, you can refer to the DevOps Loop README file.
You have installed DevOps Loop on IBM Red Hat OpenShift.
You can add users and manage user access by logging in to the Keycloak instance that is installed with DevOps Loop. See User access and administration using Keycloak.