Upgrading from 2022.2

Upgrade IBM Cloud Pak® for Integration from version 2022.2 to version 2022.4.

Important: Upgrading to 2022.4 requires that your installation is already at version 2022.2. If upgrading from an earlier version, upgrade to 2022.2 first.
Attention: Before upgrading, confirm that you are using automatic approvals for the operators, because any manual approvals can block the upgrade of Cloud Pak for Integration capabilities. For more information on approval strategies, see Installing the operators by using the Red Hat OpenShift console or Installing the operators by using the CLI. For more information on controlling operator upgrades, see Adding catalog sources to a cluster.

To perform the upgrade, you must be a cluster administrator. For more information, see Roles and permissions.

Generating an upgrade plan

An upgrade plan guides you through the upgrade of your Cloud Pak for Integration installation to a target version. Begin the upgrade process by generating an upgrade plan 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 2022.4. 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 using the CLI

  1. Log in to the OpenShift CLI.

  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 --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 2022.4 \
      --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.

Generating an upgrade plan using the Platform UI

Using the Platform UI to generate an upgrade plan is only possible once the Platform UI is upgraded to version 2022.4.1 or later. Therefore, this option can only be used once you have completed the upgrade of the Platform UI (the first step in Upgrading the capabilities.

Once the Platform UI is upgraded, 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.

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 procedure in Adding catalog sources to a cluster to update the catalog sources and images for the latest 2022.2 patch release.

Patching catalog sources and images for the 2022.4 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.

  • Otherwise, you must update the catalog sources and images for the 2022.4 release. In Adding catalog sources to a cluster, follow all tasks in the procedure that are applicable for your environment.

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: The latest versions of this operator might not be visible in the Installed Operators pane. Solution: For Project, select the namespace where the Cloud Pak for Integration operators are installed, and search for the subscription object for the Redis operator.

Upgrading the operators

Once the dependencies are upgraded, upgrade the operators to the channels that are part of the 2022.4 release, using the procedure in Upgrading operators. You can upgrade directly to the 2022.4 channels; there is no 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 2022.4 channels, you can upgrade the capabilities.

Upgrading the capabilities

Once all the operators are upgraded, upgrade your instances of capabilities (for example, API management or messaging) following this order:

  1. Upgrade the Platform UI instance to the 2022.4 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 2022.4 version. This must be done before upgrading any instances of the gateway capability (DataPower Gateway). For detailed instructions, see Upgrading API management.

  3. Upgrade the other instances of capabilities to 2022.4 versions. For detailed instructions, 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 2022.4 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 2022.4 release, it is no longer in support. Upgrade to version 4.12 after the upgrade to Cloud Pak for Integration 2022.4 is complete.

To upgrade OpenShift, confirm that the latest available fixpacks for the 2022.4 release are applied, then follow the instructions in Upgrading Red Hat OpenShift.

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.