Operator, CASE, and platform requirements for upgrading

Before you upgrade API Connect on OpenShift Container Platform, verify that you are using the correct operator, CASE file (for air-gapped upgrades), and OpenShift version.

Supported versions of operators for API Connect

Table 1 lists the operators that are used for the newest version of API Connect

Table 1. Operators for installing and upgrading API Connect
API Connect version API Connect Operator channel API Connect Operator version Data Power version DataPower Operator version Foundational services CASE version
10.0.8.0 v5.2-sc2 5.2.0 10.6.0.0 1.11.0 4.6.3

CASE versions required for air-gapped installation and upgrade

Table 2 lists the required CASE file for each API Connect release:

Table 2. CASE versions for air-gapped deployments
API Connect version API Connect CASE version Foundational services CASE version EDB CASE version
10.0.8.0 5.2.0 4.6.3 5.0.0

Supported versions of Red Hat OpenShift Container Platform

Table 3 provides a quick reference of the supported OpenShift versions for API Connect:

Table 3. API Connect and OpenShift Container Platform (OCP) compatibility
API Connect version OCP 4.10 OCP 4.12 OCP 4.14 OCP 4.15 OCP 4.16
10.0.5.4 Checkmark Checkmark      
10.0.5.5 Checkmark Checkmark Checkmark    
10.0.5.6   Checkmark Checkmark    
10.0.5.7   Checkmark Checkmark    
10.0.5.8   Checkmark Checkmark   Checkmark
10.0.6.0 Checkmark Checkmark      
10.0.7.0   Checkmark Checkmark    
10.0.8.0   Checkmark Checkmark Checkmark Checkmark

Upgrading OpenShift to support a newer version of API Connect

When you upgrade API Connect, both your current deployment and your target release must support the same version of OpenShift. After the API Connect upgrade, you can optionally update OpenShift to the highest version supported by the new release of API Connect.

During the upgrade process, it is possible that API Connect is temporarily running on an unsupported version of OpenShift because you must upgrade API Connect before you upgrade OpenShift.

For example, suppose that your current deployment is running API Connect 10.0.5.4 on OpenShift 4.10 and you want to upgrade to API Connect 10.0.8.0 on OpenShift 4.14. Both versions of API Connect support OpenShift 4.12, so on the API Connect 10.0.5.4 deployment, you must upgrade OpenShift to 4.12 before you can upgrade to API Connect 10.0.8.0. After you complete the API Connect upgrade to 10.0.8.0, you can optionally upgrade to the highest supported version of OpenShift.

In this scenario, the upgrade path is as follows:
  1. On the API Connect 10.0.5.4 deployment, upgrade OpenShift to 4.11 and then 4.12 (interim upgrades are required).

  2. Upgrade API Connect 10.0.5.4 to API Connect 10.0.8.0.

  3. Optionally upgrade OpenShift from 4.12 to 4.13, and then 4.14.

For OpenShift upgrade instructions, see the Red Hat OpenShift documentation.