Operator, CASE, and platform requirements

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

Table 1 lists the operator, operand, and CASE information that applies to API Connect.

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
12.1.1.0	v8.0	8.0.0	11.0.0.x, 10.6.0.x	1.18.x, 1.11.x	4.19.1

You can run the API Connect operator and subsystems at different versions. The following table shows the supported combinations:

Table 2. API Connect versions supported by the API Connect operators.
API Connect Operator version	API Connect version
8.0.0	12.1.1.0
7.3	12.1.0.3
7.2	12.1.0.2
7.1	12.1.0.1
7.0.0	12.1.0.0
6.2.0	10.0.11.0
6.1.0	10.0.10.0
6.0.0	10.0.9.0
5.3.0	10.0.8.1 10.0.8.0

CASE versions required for air-gapped installation and upgrade

Note: There is no need to install a separate EDB case version during the deployment process as the EDB images are included within the API Connect case package.

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

Table 3. CASE versions for air-gapped deployments
API Connect version	API Connect CASE version	Foundational services CASE version
12.1.1.0	8.0.0	4.19.1

Supported versions of Red Hat OpenShift Container Platform

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

Table 4. API Connect and OpenShift Container Platform (OCP) compatibility
API Connect version	OCP 4.14	OCP 4.16	OCP 4.18	OCP 4.19	OCP 4.20	OCP 4.21	OCP 4.22
12.1.1.0

Note: OCP version 4.16 or later is required to deploy Nano Gateway.