Upgrading from 2022.2

Attention: Now that IBM Cloud Pak® for Integration 16.1.0 has been released, do not upgrade to 2023.2 when upgrading from 2022.2. Upgrades from 2022.2 to 2023.2 should no longer be started. Upgrade directly from 2022.2 to 16.1.0 by using the procedure in Upgrading from 2022.2.

Generating an upgrade plan

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 can include:

Important: To ensure a successful upgrade, complete all tasks in the generated order. After you complete each upgrade step, regenerate the upgrade plan to get updated guidance and validate that you can proceed to the next step.

Generating an upgrade plan by using the CLI

  1. Log in to the 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 following 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, set the CP4I_NAMESPACE variable in step 4 to the namespace for another instance and repeat the step as needed.

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

Removing integration tracing

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.

Patching catalog sources and images for the 2022.2 release

The first step for upgrade is to patch the 2022.2 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.

When the catalog sources and images are updated with the latest 2022.2 patch, you can proceed with the next section.

Patching catalog sources and images for the 2023.2 release

  • If you have an online installation and are using the IBM Operator Catalog (some installations), 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.

Upgrading dependencies

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.

Troubleshooting: You may not find the latest versions of this operator in the Installed Operators panel. Solution: For Project, select the namespace where the Cloud Pak for Integration

Upgrading the operators

After the dependencies are upgraded, upgrade the operators to the channels that are part of the 2023.2 release, using the procedure in Upgrading operators. You can upgrade directly to the 2023.2 channels; you don't need to go through each intermediate channel.

Important: To ensure a successful upgrade, it is essential that you carefully follow the procedure in Upgrading operators and review all provided information.

After all the operators you intend to use are upgraded to the 2023.2 channels, upgrade the capabilities.

Upgrading the capabilities

After all the operators you intend to use are upgraded, upgrade your instances of capabilities (for example, API management or messaging) in this order:

  1. Upgrade the Platform UI instance to the 2023.2 version by following the "Upgrading the Platform UI instance" section in Upgrading the Platform UI.
    Important: Wait until the Platform UI instance is Ready before upgrading any other capabilities.
  2. Upgrade all instances of the API management capability (IBM API Connect operator), if used, to the 2023.2 version. This must be done before upgrading any instances of the gateway capability (DataPower Gateway). For more information, see Upgrading API management.

  3. Upgrade the other instances of capabilities to 2023.2 versions. For more information, see Upgrading capabilities.

Once all capabilities are upgraded, you can upgrade Cloud Pak foundational services.

Moving to specific catalog sources for each operator (optional)

If you have an online installation from a previous release, and you are using the IBM Operator Catalog, use the procedure in Moving to specific catalog sources for each operator to move to specific catalog sources for each operator.

Upgrading IBM Cloud Pak foundational services

IBM Cloud Pak foundational services version 3.19.x is compatible with the 2023.2 release, so you can stay on that version. However, if you wish to upgrade your Cloud Pak foundational services to version 3.23, follow the instructions in Upgrading IBM Cloud Pak foundational services.

Upgrading OpenShift beyond 4.10

Although OpenShift Container Platform version 4.10 is compatible with the 2023.2 release, it is no longer in support. Upgrade to version 4.12 after the upgrade to Cloud Pak for Integration 2023.2 is complete.

To upgrade OpenShift, follow the instructions in Upgrading Red Hat OpenShift.

Validating that the License Service is still installed

Depending on how you previously installed the License Service, it might have been uninstalled during the upgrade.

Validate if the License Service is still installed with:

oc get IBMLicensing -A

If nothing returns, re-install the following the instructions in Deploying License Service.