Installing

A IBM Cloud Pak® for Integration installation consists of a Red Hat® OpenShift® Container Platform cluster with one or more Cloud Pak for Integration operators installed and one or more instances of Platform UI deployed.

Before you begin

This guide assumes that you have prepared a Red Hat OpenShift cluster with appropriate storage (following the guidance in the Planning section.

Installation options

If you want to find out more about methods of installation where the steps are partially (or completely) automated for you, see Installation options.

If you are installing Cloud Pak for Integration on an internet-connected cluster by using the OpenShift web console, you can use Express installation to get up-and-running quickly.

Installation procedures

The following is a description of all procedures that are required to install Cloud Pak for Integration. All of these procedures are included in the express installation method described in the previous section, except for deploying instances (which must be done as a separate procedure).

Mirror the images

If your cluster is in a restricted (air-gapped) network environment, follow the steps in Mirroring images for an air-gapped cluster.

Add the catalog sources

Make the operators available to your cluster by following the steps in Adding catalog sources to a cluster.

Install the operators

An operator must be installed for each instance type before it can be deployed. Use the applicable procedure:

Add the entitlement key

If you are using an internet-connected cluster, you need to add your entitlement key to namespaces where you want to deploy instances so that images can be pulled from the IBM Entitled Container Fulfillment Registry. Use the applicable procedure:

Deploy the Platform UI

Deploy and manage your instances from a central location. Use the applicable procedure:

Deploy instances that you intend to use.

For more information, see Deploying instances.

Troubleshooting your installation

For known issues and workarounds, see Known limitations.

To obtain logs or open a support case, see Troubleshooting.