Upgrading to Version 2020.3.1

Upgrading Red Hat OpenShift

Cloud Pak for Integration version 2020.3.1 requires Red Hat OpenShift 4.4 (minimum version).

Upgrade Red Hat OpenShift to version 4.4. See Updating a cluster between minor versions in the Red Hat OpenShift documentation.

Upgrading IBM common services

Note: For users of the Operations Dashboard, the common services upgrade refreshes the CA certificate used internally to access common services. If you use the Operations Dashboard and do not plan on upgrading it immediately, you must update the Operations Dashboard with the new CA certificate.

To do this, log into the Openshift command line and run these commands:

// Assign base64 certificate to env var
export CERT=`oc get secret cs-ca-certificate-secret -n ibm-common-services  -o jsonpath='{.data.ca\.crt}'`

// Patch the Operations Dashboard secret
oc patch secret icp4i-od-oidc-secret -p '{"data": {"icp_ca_chain.crt": "'${CERT}'"}}' -n <NAMESPACE>

// Restart the pod
oc delete pod <RELEASE_NAME>-ibm-icp4i-tracing-prod-0 -n <NAMESPACE>

Once the pod has restarted and all nine of its containers are running, you can view the Dashboard.

Upgrading IBM Common Services to high availability

For a cluster to have high availability, the associated common services instance must also be highly available, and this can only be achieved if an instance of common services is either on a medium or large cluster. By default, when upgrading the version of common services, the upgrade field is set as as-is, meaning the previous size of the common service instance is passed down to the upgraded version.

To upgrade common services to high availability, we do the following in Red Hat Open Shift Container Platform (OCP):

  1. Navigate to the Installed Operators page and change the namespace to ibm-common-services.

  2. Select IBM Common Service Operator and then select CommonService from the API tabs.

  3. Select the instance named common-service and navigate to the YAML tab. In the spec: size: field, enter either "medium" or "large".

An example of a medium instance of common services is shown below, with all non-optional fields:

apiVersion: operator.ibm.com/v3
kind: CommonService
metadata:
  name: common-service
  namespace: ibm-common-services
spec:
  size: medium

Upgrading the Platform Navigator

The Platform Navigator stores no persistent data, so to upgrade the Platform Navigator from the Helm release to the operator based release an administrator can:

  1. If not already done for a previous release, uninstall the Helm release in the Common Services UI or the Helm CLI. See Uninstalling.

  2. Deploy a new Platform Navigator using the operator. See Platform Navigator deployment

Note: To perform the upgrade with no downtime, you can install the new Platform Navigator before removing the old one, but you must use a different namespace.

Upgrading other component products

Below are links to upgrade information for component products.

Asset Repository

See Upgrading in the Asset Repository documentation.

Operations Dashboard

See Upgrade in the Operations Dashboard documentation.

IBM API Connect

IBM API Connect cannot be upgraded from the Helm based release to the Operator based release. Instead, remove the Helm deployment and create a new deployment using the operator.

IBM App Connect

See Upgrading or migrating from previous releases in the IBM App Connect documentation.

IBM Aspera High Speed Transfer Server

See Upgrading HSTS.

IBM DataPower Gateway

See Release notes in the IBM DataPower Operator documentation.

IBM Event Streams

To upgrade Event Streams within Cloud Pak for Integration, you need to update the version within the Platform Navigator UI.

  1. Click Runtimes, then click the overflow menu at the end of the row for the Event Streams instance, and select Change version.

  2. Select the new version and click Change version.

IBM MQ

See Upgrading in the IBM MQ documentation.