Upgrading from 2022.2

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 components 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

4. 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.

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.

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.

Effective with Cloud Pak for Integration 16.1.0 , integration tracing (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.

To remove integration tracing, you need to remove all of the following:

• the integration tracing configuration from any integration instance

• the integration tracing instance

• the Cloud Pak for Integration Operations Dashboard operator.

For instructions on removing these required elements (configuration, instance, and operator), see the upgrade plan that you generated in the "Generating an upgrade plan" step. The upgrade plan confirms that integration tracing is being used and then provides you with the correct sequence of CLI commands to remove it.

Apply a fix pack for the 2022.2 release 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 on applying 2022.2 fix packs, see Applying fix packs between major releases.

If your current installation of Cloud Pak for Integration does not have the IBM Cloud Pak for Integration operator, and you have any deployed instance type that uses IBM Cloud Pak foundational services identity and access management, you must install this operator. Follow the procedure in Installing the operators by using the Red Hat OpenShift console.

The upgrade plan confirms whether or not you need to install the operator.

If you are using API management, install the cert-manager Operator for Red Hat OpenShift, in the cert-manager-operator namespace (project). For more information, see Installing the cert-manager Operator for Red Hat OpenShift.

• 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 tasks in Adding catalog sources to a cluster that are applicable for your environment. When the catalog sources and images are updated with the latest 16.1.0 content, regenerate the upgrade plan to get the next step.

1. So that user migration can occur, use one of the following methods for triggering Keycloak installation:

   • If you already have the Platform UI deployed, and you upgraded it when prompted by the upgrade plan, you have completed this step. The Platform UI triggers the installation of Keycloak automatically during upgrade.

   • If you do not currently have the Platform UI, deploy it when the upgrade plan prompts you to upgrade users (the "Configuring the new identity and access management system" step). The compute resources of the Platform UI are minimal. The Platform UI automatically triggers the installation of Keycloak when you upgrade Cloud Pak for Integration by using the upgrade plan in Upgrading from 2023.4 or Upgrading from 2022.2. For more information, see Deploying the Platform UI.

   • Initiate the installation of Keycloak manually. For more information, see Installing the identity and access management system when the Platform UI is not installed.

2. Migrate your identity and access management configuration. For more information, see Migrating users from IAM to Keycloak.

   Important: If you are using API management (IBM API Connect), make sure that the usernames from the identity provider that is used with the previous identity and access management system are preserved correctly when configuring Keycloak. For more information, see the topics on configuring identity providers under Managing users and groups.