Upgrading from 2023.4

Upgrade IBM Cloud Pak® for Integration from version 2023.4 to version 16.1.0 by generating an upgrade plan. To upgrade, you must be an OpenShift cluster administrator. For more information, see OpenShift roles and permissions.

Attention: AI test generation is removed in Cloud Pak for Integration 16.1.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.

Before you begin

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

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. Initially, use the procedure in Generating an upgrade plan by using the CLI.

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.1.0. These tasks can include:

  • Applying the correct fix pack for the 2023.4 release

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

  • Upgrading the operators

  • Upgrading the Cloud Pak foundational services

  • Upgrading the Platform UI

  • Upgrading the instances

  • Upgrading OpenShift beyond 4.12 (optional)

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

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 will be 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 instances 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.1.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 A specific namespace on the cluster installation in 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

After you complete the step to upgrade the Platform UI, 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 2023.4 release that supports the upgrade process

Apply the correct fix pack for the 2023.4 release that supports the upgrade process. The upgrade plan explains what the required fix packs are and whether the Cloud Pak for Integration installation meets the requirements. For more information on applying 2023.4 fix packs, see Applying fix packs between major releases.

Upgrading the catalog sources and mirroring images for the 16.1.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.1.0 release by following all steps in Applying fix packs between major releases that are applicable for your environment.

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