Upgrading the operator in the OpenShift console

You can upgrade the operator in the OpenShift Operator Hub to the new version before you apply your custom resource upgrades.

About this task

New releases of the 21.0.3 catalog are published in the IBM operator catalog. If you installed, for example a Cloud Pak for Business Automation 21.0.2 operator on your cluster, then the instance appears in Installed Operators. You can see the Subscription details after selecting the operator as shown in the following screen capture.

The channel in 21.0.1 used stable, V21.1 in 21.0.1-IF001, V21.2 in 21.0.2, and it changed to V21.3 in 21.0.3. Select the V21.3 channel to upgrade the operator to 21.0.3.

1. In the Subscription tab, click to edit the Channel.

   The current channel appears selected, and any new channels appear in the Update Channel list.

2. To change the subscribed channel, select the v21.3 channel and click Save.

   The Cloud Pak for Business Automation operator is automatically updated to 21.0.3.

3. If you have any subscriptions set to manual, then you must approve any pending operator updates.

   It is not recommended to set subscriptions to manual because it can make the upgrade more error prone if some of the operator updates are not approved. By default, all subscriptions are set to automatic.

4. Click Installed Operators to see the updated operator.
   

   If the Cloud Pak for Business Automation operator upgrade continues to show the status "Upgrading", then you might need to intervene.

   To resolve the issue, remove the previous version of the operator by clicking the overflow menu in the last column, click Uninstall Operator, and then install the operator again from the IBM Cloud Pak® for Business Automation catalog.

   1. Delete the operators in your namespace.
   2. Delete the catalog source (ibm-cp4a-operator-catalog).
   3. Rerun the cluster admin script to reapply the catalog source.
   4. Reinstall the operators from OperatorHub.