Upgrading the operator

You must upgrade the operator to the new version before you apply your custom resource upgrades.

Before you begin

To prevent any connection problems during the upgrade, make sure that the passwords that you use for databases and LDAP are not about to expire and refresh them if they are. For example, an out-of-date ldapPassword key in the LDAP bind secret does stop UMS pods from restarting. These pods can also prevent other pods that integrate with UMS from restarting. The LDAP bind secret "ldap-bind-secret" is set in the lc_bind_secret parameter in the following ldap_configuration section.

ldap_configuration:
   lc_bind_secret: ldap-bind-secret

Note: For Automation Document Processing upgrades, complete the preparation steps in Upgrading IBM Automation Document Processing before you upgrade the operator.

About this task

Important: If you are looking to upgrade a deployment that you installed with the operator lifecycle manager (OLM) in 20.0.3, then you must delete the previous version of the IBM operator catalog and install the new catalog into the Operator Hub. For more information, see Installing an Enterprise deployment in Operator Hub.

Tip: When you upgrade from any version, you can upgrade the operator and keep the container image tags at the previous versions.