Upgrading from 2023.4

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

Important: Upgrading to version 16.1.0 requires that your installation is already at version 2022.2 or 2023.4. If upgrading from an earlier version, upgrade to 2022.2 or 2023.4 first. For instructions, go to the Upgrading page and select the procedure for the version from which you are upgrading.

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

Attention: AI test generation is temporarily 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. You may want to delay upgrade until it becomes available.

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 by using the CLI. As you move through the upgrade process, you regenerate the plan to get updated guidance and to validate that you can proceed to the next step. After you complete the step to upgrade the Platform UI, you can regenerate the plan by using either the Platform UI or the CLI.

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. For more information, see Upgrading operators.
Upgrading Cloud Pak foundational services. For more information, see Upgrading IBM Cloud Pak foundational services.
Upgrading the Platform UI. For more information, see Upgrading the Platform UI.
Upgrading the instances. For more information, see Upgrading instances.
Upgrading OpenShift beyond 4.12 (optional). For more information, see Upgrading Red Hat OpenShift.

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.

Generating an upgrade plan by using the CLI

Log in to the Red Hat OpenShift CLI.
```
oc login
```
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
```

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 \
  --debug

If you have 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 cluster. Repeat the command as needed.
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 regenerate your 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 regenerate the upgrade plan.

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), update the catalog sources and images for the 16.1.0 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 16.1.0 content, you can proceed with the upgrade.

Parent topic:

Upgrading