Upgrading the IBM Cloud Pak®

Upgrade IBM Cloud Pak® for Multicloud Management from a previous version to IBM Cloud Pak® for Multicloud Management 2.3.x.

Notes:

The subscription approval is automatic by default. In this case, the previously-installed IBM Cloud Pak for Multicloud Management 2.3.x can be upgraded to the latest Fix Pack level automatically.
If you upgrade your IBM Cloud Pak for Multicloud Management from version 2.2.x, follow the steps in Online upgrade and Offline (airgap) upgrade.
If you want to control which IBM Cloud Pak for Multicloud Management Fix Pack you want to install in your cluster, you need to switch the subscription approval to manual as described in Optional: switch the subscription approval to manual. Then, you can upgrade by following the steps in Upgrading to Fix Pack 2, Upgrading to Fix Pack 3 or 4, Upgrading to Fix Pack 5, Upgrading to Fix Pack 6, Upgrading to Fix Pack 7, and Upgrading to Fix Pack 8.
You need to do the post-upgrade tasks, and verity the upgrade for all these scenarios.
License Advisor is sunset in version 2.3 Fix Pack 5 and is not longer available with IBM Cloud Pak for Multicloud Management. To track license usage of your IBM® containerized software, use License Service Reporter. For more information, see Monitoring license usage of IBM products.
IBM Cloud Pak for Multicloud Management no longer supports the legacy subscription-based applications. All the legacy applications need to migrate manually to hybrid applications.

Supported upgrade path

You can upgrade only from IBM Cloud Pak for Multicloud Management Version 2.2.x to Version 2.3.x and later.

Prerequisites

Upgrade Red Hat® Advanced Cluster Management for Kubernetes to version 2.2.x.

Before you upgrade the IBM Cloud Pak for Multicloud Management, make sure that you upgrade the IBM Cloud Pak foundational services to version 3.6.x. For more information, see Upgrading IBM Cloud Pak foundational services online. Use the following command to check the version:

oc get csv -n openshift-marketplace | grep common

From the following sample output, the common services version is 3.6.3:

NAME                              DISPLAY                         VERSION   REPLACES                                      PHASE
ibm-common-service-operator.v3.6.3                IBM Cloud Platform Common Services            3.6.3                ibm-common-service-operator.v3.6.2                Succeeded

Before you upgrade to a specific IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack , you need to take a backup of the cassandra database so that Monitoring can be restored successfully after the IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack is rolled back. For more information, see Backing up and restoring Cassandra.
If the management-monitoring configmap monitoring-sizing-size0 or Monitoring-sizing-size1 is changed, you need to back up the configuration by running the following command, and save the file.
```
oc get configmap monitoring-sizing-size-<x> -n management-monitoring -o yaml >/tmp/before-monitoring-sizing-sizeX.yaml
```
Changes between releases might have an impact on your hardware requirement. Ensure that you meet the current System requirements before you upgrade.

Limitation: All agent metrics that were stored in version 2.2.x will be lost after upgrading to version 2.3.x.