Minimum Versions of Red Hat Integration Components Required for OCP 4.6
OpenShift Container Platform (OCP) 4.6 is adopting the new bundle format for operators as standard and is dropping support for the old package manifest format. You must therefore ensure that any installed operators for Red Hat Integration components are upgraded to a version that supports the new bundle format. For some products the operators must be upgraded before you upgrade your OpenShift cluster, while for other products the operators must be upgraded after you upgrade your OpenShift cluster.
The following table provides details of the product versions and operator versions for the Red Hat Integration products that need to be upgraded before you upgrade your cluster to OCP 4.6. Some products require a minimum version to be installed to get support for the new bundle format in OCP 4.6. For products that do not require a specific minimum version, you should be guided by the relevant supported configurations matrix.
| Product component | Minimum product version | Operator name | Recommended operator channel |
|---|---|---|---|
| AMQ Streams | See supported configurations | Red Hat Integration - AMQ Streams | stable |
| AMQ Interconnect | 1.9.0 | Red Hat Integration - AMQ Interconnect | 1.2.0 |
| AMQ Online | 1.6.0 | Red Hat Integration - AMQ Online | stable |
| AMQ Broker | See supported configurations | Red Hat Integration - AMQ Broker | current |
| 7.4 | Red Hat Integration - AMQ Broker LTS | alpha | |
| 3scale | See supported configurations | Red Hat Integration - 3scale | threescale-2.9 |
| See supported configurations | Red Hat Integration - 3scale APIcast gateway | threescale-2.9 | |
| Service Registry | 1.0.2 | Red Hat Integration - Service Registry Operator | serviceregistry-1.0 |
Log in as an administrator to the OpenShift console and, for each of the installed operators, select the operator channel given in the preceding table. If the operator's approval strategy is set to Automatic, the operator upgrade starts automatically. But if the approval strategy is set to Manual, you must manually approve the update request from the OpenShift console. You are now ready to perform the upgrade to OCP 4.6.
The following table provides details of the product versions and operator versions for the Red Hat Integration products that need to be upgraded after you upgrade your cluster to OCP 4.6.
| Product component | Minimum product version | Operator name | Recommended operator channel |
|---|---|---|---|
| Fuse Console | 7.7.1 | Red Hat Integration - Fuse Console | fuse-console-7.7.x |
| API Designer (Apicurito) | 7.7.1 | API Designer | fuse-apicurito-7.7.x |
| Fuse Online | 7.7.1 | Red Hat Integration - Fuse Online | fuse-online-7.7.x |
| Camel K | TP2 | Red Hat Integration - Camel K | techpreview |
On the newly upgraded OCP 4.6 cluster, log in as an administrator to the OpenShift console and, for each of the installed operators, select the operator channel given in the preceding table.
Note that for the Fuse 7.7 operators on OCP 4.6, the names of the operator channels have changed. If you cannot see the new operator channels after upgrading OpenShift to OCP 4.6, see known issue ENTESB-15232 for details of how to refresh the operator channels. If the approval strategy is set to Manual, you will need to approve the update requests from the OpenShift console.