Upgrading IBM Cloud Pak for AIOps
Upgrade an existing online or offline deployment of IBM Cloud Pak® for AIOps 4.2.0 or later to 4.3.0.
You cannot use these instructions to upgrade deployments of IBM Cloud Pak for AIOps 4.1.2 or earlier.
Upgrade paths
IBM Cloud Pak for AIOps uses a versioning system of X.Y.Z, where X=version, Y=release, and Z=patch. For example, IBM Cloud Pak for AIOps 4.4.1 is version 4, release 4, patch 1. IBM Cloud Pak for AIOps upgrades can be release upgrades or patch upgrades.
You can upgrade by a maximum of one release at a time. If the release that you want to upgrade from is more than one release behind the release that you are upgrading to, then you must upgrade sequentially. For example, you cannot upgrade directly from IBM Cloud Pak for AIOps 3.7.0 to v4.3.0, you must use the following sequence:
- Use the v4.1.2 documentation to upgrade from IBM Cloud Pak for AIOps 3.7.0 to v4.1.2.
- Use the v4.2.1 documentation to upgrade from IBM Cloud Pak for AIOps 4.1.2 to v4.2.1.
- Use the v4.3.0 documentation to upgrade from IBM Cloud Pak for AIOps 4.2.1 to v4.3.0.
Controlling upgrade
Patch upgrades
Online deployments
Upgrades of online IBM Cloud Pak for AIOps deployments to a higher patch, for example from IBM Cloud Pak for AIOps 4.2.0 to 4.2.1, complete automatically if catalog polling is enabled. You elect to enable or disable catalog polling when
you install IBM Cloud Pak for AIOps, and you can change this setting after installation if necessary. Automatic patch upgrade can also occur if you have not fixed the ibm-operator-catalog CatalogSource to a specific image
and the ibm-operator-catalog pods are restarted, even if catalog polling is disabled.
If you do not want your IBM Cloud Pak for AIOps deployment to upgrade automatically when newer patches are available, then you must disable catalog polling and pin the image to a specific version. For more information, see Configuring automatic patch upgrades.
Offline deployments
Upgrades of offline IBM Cloud Pak for AIOps deployments to a higher patch do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Release upgrades
Online deployments
Upgrades of online IBM Cloud Pak for AIOps deployments to a higher release, for example from IBM Cloud Pak for AIOps 4.2.0 to 4.3.0 do not complete automatically, even if catalog polling is enabled. For a release upgrade, catalog polling must be enabled and the channel subscription must also be manually edited.
Offline deployments
Upgrades of offline deployments to a higher release version do not occur automatically, as the updated installation images must be manually mirrored to the offline repository first.
Upgrade procedure
Important: If you are planning to upgrade Red Hat OpenShift as part of an upgrade to IBM Cloud Pak for AIOps 4.3.0, then you must complete the IBM Cloud Pak for AIOps upgrade before you upgrade Red Hat OpenShift.
The upgrade procedure depends on whether your deployment is an online or offline (air-gapped) deployment. For more information about online and offline deployments, see Installing IBM Cloud Pak for AIOps.
Online deployments
You can upgrade an online deployment of IBM Cloud Pak for AIOps with the Red Hat OpenShift console or command-line interface (CLI).