Express installation

If you are installing IBM Cloud Pak® for Integration on an online OpenShift cluster by using the OpenShift web console, these steps will get you up-and-running quickly. This topic covers all phases of installation up to, but not including, deploying instances.

Before you begin

You must be an OpenShift cluster administrator to use this procedure.
Create a namespace called ibm-common-services.
The following must be true of your OpenShift cluster and storage:
- The 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.14, 4.15, 4.16, 4.17, or 4.18.
- 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.

About this task

This procedure uses All namespaces on the cluster mode. In this mode, operators are installed in the openshift-operators namespace.

If you prefer not to use the express installation, start your installation here:

Adding catalog sources to an OpenShift cluster, if your OpenShift cluster is connected to the internet.
Mirroring images for an air-gapped OpenShift cluster, if your OpenShift cluster is not connected to the internet.

Procedure

Add the catalog sources.

Log into your OpenShift cluster using the oc login command and your user credentials:
```
oc login <openshift_url> -u <username> -p <password> -n <namespace>
```

Apply the catalog source files for the IBM Cloud Pak for Integration and IBM Cloud Pak foundational services operators:

oc apply --filename https://raw.githubusercontent.com/IBM/cloud-pak/master/repo/case/ibm-integration-platform-navigator/8.0.7/OLM/catalog-sources.yaml

oc apply --filename https://raw.githubusercontent.com/IBM/cloud-pak/master/repo/case/ibm-cp-common-services/4.6.17/OLM/catalog-sources.yaml

Confirm that the catalog sources have been created in the openshift-marketplace project/namespace:
```
oc get catalogsource -n openshift-marketplace
```

Install the operators.

Create the Subscription resources for the IBM Cloud Pak for Integration and IBM Cloud Pak foundational services operator:

cat <<EOF | oc create -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ibm-integration-platform-navigator
  namespace: openshift-operators
  labels:
    backup.integration.ibm.com/component: subscription
spec:
  channel: v8.0
  name: ibm-integration-platform-navigator
  source: ibm-integration-platform-navigator-catalog
  sourceNamespace: openshift-marketplace
---
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: ibm-common-service-operator
  namespace: openshift-operators
  labels:
    backup.integration.ibm.com/component: subscription
spec:
  channel: v4.6
  name: ibm-common-service-operator
  source: opencloud-operators
  sourceNamespace: openshift-marketplace
EOF

Repeat this step to install other operators that provide the instances you want to use. For example, if you install the IBM API Connect operator now, you can deploy API Connect cluster instances later. For more information, see "Operators available to install" in Installing the operators by using the Red Hat OpenShift console.

Obtain your entitlement key.
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>
```
Add a global pull secret for all namespaces.

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.
Deploy the IBM Cloud Pak Platform UI.
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.
  
  Figure 1. 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.

What to do next

Now that you have installed Cloud Pak for Integration, you can use the Platform UI to deploy instances. Before you can deploy an instance, you need to add the catalog source and install the operator that corresponds to that instance. For more information, see the following: