Upgrading from 2022.4

An upgrade plan guides you through the upgrade of your Cloud Pak for Integration installation to a target version. Generate an upgrade plan by using the CLI or the Platform UI.

When the process is complete, you get a sequence of tasks (the upgrade plan) that are required for upgrading the Cloud Pak for Integration installation to 2023.2 . These tasks can include:

• Removing integration tracing

• Patching catalog sources and images for the 2022.4 release

• Patching catalog sources and images for the 2023.2 release

• Upgrading dependencies

• Upgrading the operators

• Upgrading the capabilities

• Upgrading IBM Cloud Pak foundational services (optional)

• Upgrading OpenShift Container Platform (optional)

Generating an upgrade plan by using the CLI

1. Log in to the Red Hat OpenShift CLI.

   oc login

2. Set the CP4I_NAMESPACE variable. For <namespace>, enter the namespace where the Platform UI is installed:

   export CP4I_NAMESPACE=<namespace>

   For example:

   export CP4I_NAMESPACE=integration

3. Start a local image. The docker command runs a check of the specific Cloud Pak for Integration installation and compares the current installed versions of components with those that are part of the target version:

   docker run --platform linux/amd64 --pull=always \
     -it -v ${KUBECONFIG:-~/.kube/config}:/kube/config \
     --env KUBECONFIG=/kube/config icr.io/cpopen/ibm-integration-upgrade-must-gather:v2 \
     --namespace ${CP4I_NAMESPACE} \
     --to 2023.2 \
     --debug

4. If you have multiple instances of the Platform UI in the same cluster, go back to the previous step and set the CP4I_NAMESPACE variable to the namespace for another instance. Repeat the command as needed.

5. After you complete each upgrade step, regenerate the upgrade plan to get updated guidance and validate you can proceed to the next step.

Generating an upgrade plan by using the Platform UI

Follow the steps in the "Generating an upgrade plan" section of Managing versions and upgrades by using the Platform UI to generate an upgrade plan.

Effective with Cloud Pak for Integration 2023.2.1 , the integration tracing capability (Cloud Pak for Integration Operations Dashboard) is removed. No further updates will be provided. If you have integration tracing deployed, removing it is your first task in the upgrade process.

Remove integration tracing by removing:

• the integration tracing configuration from any integration capability's custom resource.

• the integration tracing instance.

• the Cloud Pak for Integration Operations Dashboard operator.

Refer to the upgrade plan generated in the "Generating an upgrade plan" step for instructions on how to remove the three required components (configuration, instance, and operator). The upgrade plan confirms whether integration tracing is being used and then provides you with the correct sequence of CLI commands to remove it.

The first step for upgrade is to patch the 2022.4 catalog sources and images on the cluster:

• If you have an online installation and are using the IBM Operator Catalog, no action is needed, because the IBM Operator Catalog polls every 45 minutes.

• If you are not using the IBM Operator Catalog (some online installations and all air-gapped installations), follow the steps in Adding specific catalog sources for each operator.

After the catalog sources and images are updated with the latest 2022.4 patch, you can proceed to the next section.

• If you have an online installation and are using the IBM Operator Catalog, you can skip this step, because the IBM Operator Catalog polls every 45 minutes.

• • If you are not using the IBM Operator Catalog (some online installations and all air-gapped installations), update the catalog sources and images for the 2023.2 release. Complete all steps in Applying fix packs between major releases that are applicable for your environment.

When the catalog sources and images are updated with the latest 2023.2 content, you can proceed with the upgrade.

The next step is to upgrade the Cloud Pak for Integration dependencies.

Operator for Redis

If using the IBM Cloud Databases Redis operator (used only for Aspera HSTS), upgrade the operator to version 1.5 or later. For the upgrade procedure, see Upgrading operators.