Skip to main content

Introduction

This checklist will help you to gather all the information that is needed for a successful installation. You need to provide the values during the installation process.

⚠warning

This checklist is only to be considered complete if you do not deviate from the defaults. For some deviations from the default you will probably need other or more pieces of information.

Prerequisites​

  1. OpenShift, Keycloak, OpenShift CLI (oc), and Helm 3.

  2. Image and Helm Chart - The DevOps Solution Workbench images, and helm chart can be accessed via the Entitled Registry and public Helm repository.

    • The public Helm chart repository can be accessed at official IBM Helm Repo and directions for accessing the DevOps Solution Workbench chart will be discussed later in this README.

    • Get a key to the entitled registry

      • Log in to MyIBM Container Software Library with the IBMid and password that are associated with the entitled software.
      • In the Entitlement keys section, select Copy key to copy the entitlement key to the clipboard.
      • An imagePullSecret must be created to be able to authenticate and pull images from the Entitled Registry. Note: Secrets are namespace scoped, so they must be created in every namespace you plan to install DevOps Solution Workbench into. Following is an example command to create an imagePullSecret named 'ibm-entitlement-key'.
      oc create secret docker-registry ibm-entitlement-key 
        --namespace [namespace_name] 
        --docker-username=cp 
        --docker-password=<EntitlementKey> 
        --docker-server=icr.io

  3. Licensing

DevOps Solution Workbench requires an installed IBM Rational License Key Server (RLKS). You must specify this RLKS server during installation.

See IBM Rational License Key Server documentation for more details.

Clock Synchronization​

The IBM DevOps Solution Workbench requires that you synchronize the clocks on each node in the cluster. The clocks must be within one second of each other. It is recommended that you use chrony to synchronize your clocks. For more information about setting up chrony, see the user documentation for your operating system.

Certificates​

It is recommended to NOT use self-signed certificates. As a feasible solution it might be sufficient to use certificates that are signed by Let's encrypt.

ℹ️note

The line length of the certificates must comply with the standard for PEM messages, with each line containing exactly 64 printable characters except the last line and 64 or fewer printable characters in the last line.