Upgrading operators

You can upgrade operators by using either the UI (OpenShift web console) or CLI:

This task must be performed by a cluster administrator. For more information, see OpenShift Roles and permissions.

Troubleshooting

  • When upgrading Cloud Pak for Integration operators, the operator pod enters a CrashLoopBackOff state

    Issue: Kubernetes garbage collection may fail to remove the associated lock file. The lock file may prevent an operator pod from running after upgrade.

    Background: For a brief description of lock files, see Leader election.

    Resolution: Delete the -lock configMap associated with the operator. This releases the lock and allows the operator pod to run.

  • Cannot find the latest versions of the IBM Cloud Databases Redis operator

    Issue: You may not find the latest versions of this operator in the Installed Operators panel.

    Resolution: For Project, select the namespace where the Aspera HSTS operator is installed, and search for the subscription object for the Redis operator.