Applying fix packs between major releases

Patch your cluster between major releases of IBM Cloud Pak® for Integration by applying the latest fix pack for 2023.4 . Apply the fix pack to the catalog sources, operators, and instances, in that order.

To get updates between releases:

Important announcements - Sign up at My Notifications.

Tips on getting the most out of Cloud Pak for Integration capabilities - Go to Cloud Pak for Integration Community Blog.

The latest fixpack versions - See "Export commands for all operators" in Adding catalog sources to a cluster (OPERATOR_VERSION=x.x.x).

Mirror fix pack images (air-gapped installations only)

In the applicable topic (Mirroring images with a bastion host or Mirroring images with a portable compute or storage device (file system)):

Follow the steps in the section, "2. Set environment variables and download CASE files".
Continue with "3. Mirror the images". Complete all steps from 3.1 to 3.4. (Don't complete "3.5. Configure the cluster".)

Apply the fix pack to catalog sources for the 2023.4 release

For online clusters, update the catalog sources and images by applying the latest 2023.4 fix pack:

If you are using the IBM Operator Catalog, no action is needed, because the IBM Operator Catalog polls every 45 minutes.
If you are not using the IBM Operator Catalog, follow the procedure in Adding catalog sources to a cluster. The patch versions on this page are updated every time a new fix pack is released, so rerunning the steps applies the latest fix packs.

For disconnected or air-gapped clusters, in Adding catalog sources to a cluster, go to the section, "Adding specific catalog sources for each operator", follow the steps to log in and export environment variables, then skip to the step for applying the the catalog sources.

Apply fix packs to operators for the 2023.4 release

Applying the fix pack to the operator for the current release involves updating to the latest operator channel.

For each operator, find the corresponding operator channel that is listed in Operator and instance versions for this release.
Update your operators to the latest 2023.4 fix pack release. Begin by confirming the channel to which each operator is subscribed. Follow steps 1-5 in Upgrading operators by using the OpenShift web console or steps 1-4 in Upgrading operators using the CLI.
- If the fix pack is on the latest (correct) channel:
  - and Automatic approval is configured, the fix is applied automatically when the catalog source is updated.
  - and Manual approval is configured (which is not recommended), accept an install plan. For more information, see "Restricting automatic updates with an approval strategy" in Installing the operators by using the Red Hat OpenShift console.
- If the fix pack is on a different channel, change the subscription to target the latest channel that is part of this release. Follow steps 6-7 in Upgrading operators by using the OpenShift web console or steps 5-6 in Upgrading operators using the CLI.

Apply fix packs to instances for 2023.4

If the spec.version of your custom resource (CR) is set to a CR channel, the instance is automatically updated to the latest fix pack when the operator is updated (as described in the previous section).

By using the Platform UI: After upgrading the operator, you get an "Upgrade available" link. Upgrade the instance by using the Upgrade panel, following the procedure for "Upgrading instances on the Integration versions and upgrades page" in Managing versions and upgrades by using the Platform UI.
By using the CLI: Edit the Customer resources by updating the spec.version to the latest version. You can find the latest version in the CR (the latest value given for status.versions.availableVersions), or by going to Operator and instance versions for this release and finding the version in the "Latest instance" column.