Chapter 2. Upgrading Fuse Online

From time to time, fresh application images, which incorporate patches and security fixes, are released for Fuse. You are notified of these updates through Red Hat’s errata update channel. You can then upgrade your Fuse images.

For OCP 4.x, use the OpenShift OperatorHub to upgrade from Fuse 7.10 to 7.11, by following the steps in Upgrading Fuse by using the OperatorHub (OCP 4.x).

You should determine whether upgrading to Fuse 7.11 requires you to make changes to your existing integrations. Even if no changes are required, you must republish any running integration when you upgrade Fuse.

Upgrading Fuse by using the OperatorHub (OCP 4.x)

Use the OpenShift OperatorHub to upgrade from Fuse Online 7.10 to 7.11.

  1. If you want to upgrade from Fuse 7.9.x to Fuse Online 7.10.1, you must first manually upgrade to Fuse 7.10.0 as described in the Upgrading from Fuse Online 7.9.x to 7.10.1 requires manual upgrade steps release note.
  2. Fuse 7.11 requires OpenShift Container Platform (OCP) 4.6 or later. If you are using OCP 4.5 or earlier, you must upgrade to OCP 4.6 or later, if you want to upgrade to Fuse 7.11 .

  3. On OCP 4.9, When you upgrade to 7.11, the following warning is displayed during the Fuse Operator upgrade process:

    W1219 18:38:58.064578 1 warnings.go:70] extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress

    This warning appears because clients (that Fuse uses for the Kubernetes/OpenShift API initialization code) access a deprecated Ingress version. This warning is not an indicator of complete use of deprecated APIs and there is no issue with upgrading to Fuse 7.11.

The upgrade process from a Fuse Online 7.10 or an earlier version to a newer Fuse Online 7.11 version depends on the Approval Strategy that you selected when you installed Fuse Online:

  • For Automatic updates, when a new version of the Fuse operator is available, the OpenShift Operator Lifecycle Manager (OLM) automatically upgrades the running instance of the Fuse Online without human intervention.
  • For Manual updates, when a newer version of an Operator is available, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Fuse Online operator updated to the new version as described in the Manually approving a pending Operator upgrade section of the OpenShift documentation.

During and after an infrastructure upgrade, existing integrations continue to run with the older versions of Fuse libraries and dependencies.

To have existing integrations run with the updated Fuse Online version, you must republish the integrations.