Express installation

• Create a namespace called ibm-common-services.

• The following is true of your cluster and storage:

  • Your Red Hat OpenShift cluster has access to the internet, so that it can pull images.

  • You are installing Cloud Pak for Integration on a cluster that is running on OpenShift Container Platform version 4.12 or 4.14.

  • The minimum resources that can be available on your cluster are 10 CPU units and 20 GB of memory.

  • You use a block storage class that supports ReadWriteOnce (RWO) access. For example, ibmc-block-gold, gp3, or ocs-storagecluster-ceph-rbd. For more information, see Storage considerations.

This task requires version 1.6.0 or later of the IBM Catalog Management plug-in, for running oc ibm-pak commands against the cluster. If you have not already installed this plugin, or if it needs updating, download it from GitHub.

1. Log into your cluster using the oc login command and your user credentials:

   oc login <openshift_url> -u <username> -p <password> -n <namespace>

2. Generate the catalog source files for the IBM Cloud Pak Platform UI.

   1. Export the variables for the command line to use:

      export OPERATOR_PACKAGE_NAME=ibm-integration-platform-navigator 
      export OPERATOR_VERSION=7.2.4
      export ARCH=amd64

   2. Download the files for the desired operator:

      oc ibm-pak get ${OPERATOR_PACKAGE_NAME} --version ${OPERATOR_VERSION}

   3. Generate the catalog sources required for this operator:

      oc ibm-pak generate mirror-manifests ${OPERATOR_PACKAGE_NAME} icr.io --version ${OPERATOR_VERSION}

   4. Apply the catalog sources for this operator to the cluster.

      oc apply -f ~/.ibm-pak/data/mirror/${OPERATOR_PACKAGE_NAME}/${OPERATOR_VERSION}/catalog-sources.yaml

3. Generate the catalog source files for IBM Cloud Pak foundational services.

   1. Export the variables for the command line to use:

      export OPERATOR_PACKAGE_NAME=ibm-cp-common-services
      export OPERATOR_VERSION=4.6.14
      export ARCH=amd64

   2. Download the files for the desired operator:

      oc ibm-pak get ${OPERATOR_PACKAGE_NAME} --version ${OPERATOR_VERSION}

   3. Generate the catalog sources required for this operator:

      oc ibm-pak generate mirror-manifests ${OPERATOR_PACKAGE_NAME} icr.io --version ${OPERATOR_VERSION}

   4. Apply the catalog sources for this operator to the cluster. This command might not return anything if there are no multi-architecture catalog sources for the components being installed:

      oc apply -f ~/.ibm-pak/data/mirror/${OPERATOR_PACKAGE_NAME}/${OPERATOR_VERSION}/catalog-sources.yaml

4. Confirm that the catalog sources have been created in the openshift-marketplace project/namespace:

   oc get catalogsource -n openshift-marketplace

1. Log into the OpenShift web console with your OpenShift cluster admin credentials. Make sure that the Administrator view is selected.

2. Click Operators > OperatorHub.

   

3. Search for and click the IBM Cloud Pak for Integration tile.

4. Click Install.

5. In the Install Operator pane:

   1. Select the 7.2 channel.

   2. Click All namespaces on the cluster to install in all namespaces on your cluster, and accept the default Installed Namespace.

   3. Select the Automatic approval strategy option.

6. Click Install.

7. Repeat steps 2-7 to install the IBM Cloud Pak foundational services operator with the v4.6 channel.

1. Go to the Entitlement keys page of the IBM Container software library.

2. In the first file, click Copy.

3. Copy the entitlement key to a safe place so that you can use it in the next section ("Adding a pull secret to a namespace").

4. (Optional) Verify the validity of the key by logging in to the IBM Entitled Registry in a container tool:

   docker login cp.icr.io --username cp --password <entitlement_key>

This task adds a pull secret for the whole OpenShift cluster.

1. Log in to the OpenShift web console. Make sure the Administrator view is selected.

2. In the navigation pane, click Workloads > Secrets.

3. Ensure that the Project is set to openshift-config.

4. In the Secrets pane, find and click pull-secret in the list of secrets.

5. Click the arrow to expand the Actions list, then click Edit Secret.

6. In the list of credentials, scroll to the end of the page and click Add credentials.

7. Enter these values in the following fields:

   • Registry server address - cp.icr.io.

   • Username field - cp.

   • Password field - the entitlement key you got in the previous section, "Obtaining your entitlement key".

8. Click Save. This update triggers a restart of all your cluster's nodes. It may take up to an hour for the change to take effect, depending on your cloud provider and the size of your cluster.

9. In the navigation pane, click Compute > Nodes to confirm the progress of the update. When all nodes have the value Ready in the Status column, your global pull secret is applied.

1. Log into the OpenShift web console with your OpenShift cluster admin credentials.

2. In the navigation pane, click Home > Overview.

3. In the Build with guided documentation section, click View all quick starts.

   

4. In the Quick Starts panel, click the tile for Getting started with the Cloud Pak for Integration.

5. In the panel that opens, follow the procedures to deploy the Platform UI.

   Tip: If you have followed all the procedures up to this point, you can skip the Prerequisites section.

Now that you have installed Cloud Pak for Integration, you can install instances. For more information, see Deploying instances.