Upgrading from version 16.1.0 or 16.1.3

Upgrade IBM Cloud Pak® for Integration from version 16.1.0 or 16.1.3 to version 16.2.0 by generating an upgrade plan.

Before you begin

Upgrading to Cloud Pak for Integration 16.2.0 requires that your installation is already at version 16.1.0 or 16.1.3. Follow the applicable path for your current version.

  • Earlier than 16.1.0, complete these tasks:

    1. Upgrade to 16.1.0. On the Upgrading page for 16.1.0, click the page link for the version from which you are upgrading and follow the procedure.

    2. Upgrade from 16.1.0 to 16.2.0 by following the steps in this topic. Begin with Generate an upgrade plan.
      Attention: AI test generation is removed in Cloud Pak for Integration 16.2.0. If you already have AI test generation deployed and you upgrade Cloud Pak for Integration, you will no longer be able to use the feature.

  • 16.1.1, upgrade to 16.1.2 first by following the procedure in Upgrading from version 16.1.0 or 16.1.1.

  • 16.1.2, upgrade to 16.1.3 first by following the procedure in Upgrading from version 16.1.0 or 16.1.2.

  • 16.1.0 or 16.1.3, upgrade from the current version to 16.2.0, as described in this topic. Begin with Generate an upgrade plan.

Generate an upgrade plan

Begin the upgrade process by generating an upgrade plan, which guides you through the upgrade of your Cloud Pak for Integration installation to a target version. You can use the CLI or use the Platform UI.

Tip: The upgrade plan in the CLI is updated more frequently.
Important: To ensure a successful upgrade, complete all tasks in the order that is provided by the upgrade plan. After you complete each upgrade step, regenerate the upgrade plan to get updated guidance and to validate that you can proceed to the next step.

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

  • Applying the correct fix pack for your current installation version

  • Upgrading OpenShift to 4.14

  • Upgrading the catalog sources and mirroring images for the 16.2.0 release

  • Upgrading the operators

  • Upgrading the Platform UI

  • Upgrading the instances

  • Upgrading OpenShift beyond 4.14 (optional)

Although the upgrade plan itself provides guidance on completing these tasks, additional information is available in Reference for steps in an upgrade plan.

Important: The upgrade plan is not aware of Cloud Pak for Integration installations on other clusters. You must generate upgrade plans on each cluster where Cloud Pak for Integration is installed.

Generating an upgrade plan by using the CLI

  1. Log in to the Red Hat OpenShift CLI.

    oc login

  2. Set the OPERATOR_NAMESPACE variable. For <namespace>, enter the namespace where the operators are installed. When installing in "All namespaces on the cluster" mode, this namespace is openshift-operators:

    export OPERATOR_NAMESPACE=<namespace>

    For example:

    export OPERATOR_NAMESPACE=openshift-operators

  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 operators and intances with the versions 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:v4 \
  --namespace ${OPERATOR_NAMESPACE} \
  --to 16.2.0 \
  --verbose

  4. If you installed operators in "A specific namespace on the cluster" mode, go back to the previous step and set the OPERATOR_NAMESPACE variable to the namespace for any other installation in "A specific namespace on the cluster" mode on this OpenShift cluster. Repeat the command as needed for other namespaces in which operators are installed.

  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 by using the Platform UI

Important:
  • If you are upgrading from version 16.1.0 and you want to use the Platform UI to generate the upgrade plan, you must first patch the Platform UI with the latest available fix pack for the current installed version. For more information, see Applying fix packs between major releases.
  • If upgrading from version 16.1.2, you must use the CLI to run the upgrade plan. After the Platform UI is upgraded to version 16.2.0, you have the option to use the Platform UI to complete the rest of the upgrade.

When the IBM Cloud Pak Platform UI is at the correct version, follow the steps in the "Generating an upgrade plan" section of Managing versions and upgrades by using the Platform UI.

Troubleshooting: If you are upgrading from version 16.1.0 and you get one or both of the following issues, your deployment of the Platform UI is not at the latest 16.1.0 fix pack:
  • The first step, "Validating that the upgrade plan tool is up to date," is not complete (it does not display a green check mark).
  • The Upgrade planning tab does not provide '16.2.0' as the target upgrade version.
To resolve the issue, apply the latest fix pack for your currently installed version. After you apply the fix pack, you can use the Platform UI to regenerate your upgrade plan. Follow the steps in the "Generating an upgrade plan" section of Managing versions and upgrades by using the Platform UI.

Reference for steps in an upgrade plan

While many of the steps that are returned in your upgrade plan provide a direct link to the applicable procedure or provide additional details, you may find it helpful to review the following sections while working through the process.

Applying the correct fix pack for the 16.1.0 or 16.1.3 release

Apply a fix pack (which corresponds to your currently installed version of Cloud Pak for Integration) that supports the upgrade process. The upgrade plan explains what the appropriate fix packs are and whether the Cloud Pak for Integration installation meets the requirements.

For more information, see the applicable instructions:

Upgrading the catalog sources and mirroring images for the 16.2.0 release

  • 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), complete these tasks:

    1. Update the catalog sources and images for the 16.2.0 release by completing all the steps in Adding catalog sources to an OpenShift cluster that are applicable for your environment.
      Tip: If you are using the IBM Operator Catalog, no action is needed, because the IBM Operator Catalog polls every 45 minutes (although applying individual catalog sources, which means using specific catalog sources for each operator, rather than the IBM Operator Catalog, is the most effective way to fully control software versioning on an OpenShift cluster).

    2. When the catalog sources and images are updated with the latest 16.2.0 content, regenerate the upgrade plan to get the next step.