Deploying IBM Cloud Pak for Integration 2019.4 on OCP 4.2

Login to the infra node (or Boot node as the case may be) and check if the oc tool is installed. If the oc tool is not installed, follow the steps below:

In the OCP console, click on ‘Command line tools’

Click on ‘Download oc’

After downloading the file ‘oc.tar.gz’, extract it using the command below, give the appropriate permission and move to /usr/bin directory

tar xzvf oc.tar.gz
chmod 755 oc
mv oc /usr/bin

oc login --server=<OCP api server> -u <ocp admin user> -p <password>

You may also login by getting the login command with a generated token. To get the login command, login to the OCP console and click on ‘Copy login command’

Click on ‘Display Token’

Copy the login command with token

Login to OCP using this login command

By default, the OpenShift Container Platform registry is secured during cluster installation so that it serves traffic through TLS. Unlike previous versions of the OpenShift Container Platform, the registry is not exposed outside of the cluster at the time of installation.

Instead of logging in to the OpenShift Container Platform registry from within the cluster, you can gain external access to it by exposing it with a route. This allows you to log in to the registry from outside the cluster using the route address, and to tag and push images using the route host.

Run the command below in a single line to expose the OCP registry:

oc patch configs.imageregistry.operator.openshift.io/cluster 
   --patch '{"spec":{"defaultRoute":true}}' --type=merge

oc get route default-route -n openshift-image-registry --template='{{ .spec.host }}'

Use the command below to check if File and Block storage classes are available to use:

oc get sc

Run the command below to verify that all OCP nodes are in ‘Ready’ state

oc get nodes

You need a version of Docker that is supported by OpenShift installed on your jump box / boot node. All versions of Docker that are supported by OpenShift are supported for the boot node. Only Docker is currently supported.

Run the steps below to install docker:

yum install docker -y
systemctl start docker
systemctl enable docker

Check the docker status

systemctl status docker

Navigate to /etc/docker/certs.d and create a folder with the same name as the external url of the registry. If ‘certs.d’ folder doesn’t exist, then create it. The name of the external url of the registry can be found using the command below;

oc get route default-route -n openshift-image-registry --template='{{ .spec.host }}'

mkdir default-route-openshift-image-registry.apps.prod3.os.fyre.ibm.com

Navigate inside this directory and run the command below in a single line to pull the certificate

ex +'/BEGIN CERTIFICATE/,/END CERTIFICATE/p' <(echo | openssl s_client -showcerts 
  -connect <external url for OCP registry>) -scq > ca.crt

For example:

ex +'/BEGIN CERTIFICATE/,/END CERTIFICATE/p' <(echo | openssl s_client -showcerts 
  -connect default-route-openshift-image-registry.apps.prod3.os.fyre.ibm.com:443) -scq > ca.crt

Restart the docker service.

Now validate that you are able to login to the OCP registry using the command below:

docker login <OCP registry url> -u $(oc whoami) -p $(oc whoami -t)

For example:

docker login default-route-openshift-image-registry.apps.prod3.os.fyre.ibm.com -u $(oc whoami) -p $(oc whoami -t)

The base product installation creates an instance of the Platform Navigator, along with the common services. All of the other components are optional and immediately available to install through the Platform Navigator. The entire product and all components run within a required Red Hat OpenShift Container Platform environment.

You have the following choices for installing IBM Cloud Pak for Integration. All downloads are available from IBM Passport Advantage.

• Download the base product and all component packages. This method can be used in air-gapped environments.
• Download the base product only. All other component packages reside in the online IBM Entitled Registry. Execute the installation procedures to install on a Red Hat OpenShift Container Platform. This method requires internet access but saves time.

Change to the installer_files/cluster/ directory. Place the cluster configuration files (admin.kubeconfig) in the installer_files/cluster/ directory. Rename the file kubeconfig. This file may reside in the setup directory used to create the cluster. If it is not available, you can log into the cluster as admin using the oc login then issue the following command.

oc config view --minify=true --flatten=true > kubeconfig

apiVersion: v1
clusters:
- cluster:
 insecure-skip-tls-verify: true
 server: https://api.prod3.os.fyre.ibm.com:6443
 name: api-prod3-os-fyre-ibm-com:6443
contexts:
- context:
 cluster: api-prod3-os-fyre-ibm-com:6443
 namespace: default
 user: admin/api-prod3-os-fyre-ibm-com:6443
 name: default/api-prod3-os-fyre-ibm-com:6443/admin
current-context: default/api-prod3-os-fyre-ibm-com:6443/admin
kind: Config
preferences: {}
users:
- name: admin/api-prod3-os-fyre-ibm-com:6443
 user:
 token: klI928FXCt-0Va8lI2h7VFLN_mwCbyIuaQa_lJ_mM8M

Extract the contents of the archive with a command similar to the following.

tar xzvf ibm-cp-int-2019.4.x-offline.tar.gz

tar xvf installer_files/cluster/images/common-services-armonk-x86_64.tar.gz -O|docker load

You need to configure your cluster by modifying the installer_files/cluster/config.yaml file. You can use your OpenShift master and infrastructure nodes here, or install these components to dedicated OpenShift compute nodes. You can specify more than one node for each type to build a high availability cluster. After using oc login, use the command oc get nodes to obtain these values. Note that you would likely want to use a worker node.

Open the config.yaml in an editor.

vi config.yaml

Update the below sections in config.yaml. Below is an example:

cluster_nodes:
 master:
 - worker3.prod3.os.fyre.ibm.com
 proxy:
 - worker4.prod3.os.fyre.ibm.com
 management:
 - worker4.prod3.os.fyre.ibm.com

Specify the Storage Class. You can specify separate storage class for storing log data. Below is an example:

# This storage class is used to store persistent data for the common services
# components
storage_class: rook-ceph-cephfs-internal

## You can set a different storage class for storing log data.
## By default it will use the value of storage_class.
# elasticsearch_storage_class:

Specify password for admin user and also specify password rule, e.g.

default_admin_password: admin
password_rules:
# - '^([a-zA-Z0-9\-]{32,})$'
- '(.*)'

Leave rest of the file unchanged unless you want to change the namespaces for respective integration capabilities. Save the file.

The value of the master, proxy, and management parameters is an array and can have multiple nodes. Due to a limitation from OpenShift, if you want to deploy on any master or infrastructure node, you must label the node as an OpenShift compute node with the following command:

oc label node <master node host name/infrastructure node host name> node-role.kubernetes.io/compute=true

Once preparation completes, run the installation command from the same directory containing the config.yaml file. You can use the command docker images | grep inception to see the value used to install.

Run the command below in single line

sudo docker run -t --net=host -e LICENSE=accept -v $(pwd):/installer/cluster:z -v 
/var/run:/var/run:z -v /etc/docker:/etc/docker:z --security-opt label:disable 
ibmcom/icp-inception-amd64:3.2.2 addon

If you are deploying as root user, you would run this command without ‘sudo’.

This process transfers the product packages from the boot node to the cluster registry. This can take several hours to complete.

Once installation is complete, Platform navigator will be available at the below endpoint:

https://ibm-icp4i-prod-integration.<openshift apps domain>/

You can use the command below to get the OCP apps domain:

oc -n openshift-console get route console -o jsonpath='{.spec.host}'| cut -f 2- -d "."

You can navigate to the Openshift console and Cloud Pak foundation by clicking on the hamburger menu

Note that if you want to use the ‘Operations Dashboard’ for your integration components, you should first provision the ‘Operations Dashboard’ instance so that you can refer to it while creating an instance of an integration capability.

In this article we have learnt the installation steps for IBM Cloud Pak for Integration on OCP 4.2.