Supported operating environment for Kubernetes
Review this information for details about the system requirements for
installing the IBM® App Connect Operator on a Kubernetes cluster, and unsupported capabilities.
Minimum requirements
The minimum requirements for installation are as follows:
- The Kubernetes version of the cluster must be 1.27.x, 1.28.x, 1.29.x, 1.30.x, 1.31.x, 1.32.x, or 1.33.x.
To receive support for IBM App Connect Operator 12.19.0, you must be running a supported version of the underlying Kubernetes platform. Operator 12.19.0 supports each listed Kubernetes version until it reaches end of life (EOL). After the EOL date, support is dropped for Operator deployments that run solely on the EOL version. For information about the Kubernetes support lifecycle and EOL dates, see Release History and Non-Active Branch history.
- Only Linux® 64-bit (x86-64) is supported.
- Helm 3 is supported.
Unsupported capabilities
The following capabilities are not supported on a Kubernetes cluster:
- The
CloudPakForIntegrationNonProductionFREE,CloudPakForIntegrationNonProduction, andCloudPakForIntegrationProductionlicenses are not supported for creating IBM App Connect instances or resources.Note:If you have purchased IBM Cloud Pak for Integration, you are entitled to use both
CloudPakForIntegration*andAppConnectEnterprise*style licenses. If you want to run the IBM App Connect Operator in a Kubernetes environment, you can independently install the Operator in your cluster and then applyAppConnectEnterprise*style licenses when you create the required instances or resources.It is also possible to use annotations to allow the use of Cloud Pak for Integration licenses when creating integration runtimes on Kubernetes. For more information, see Using Cloud Pak for Integration licenses with integration runtimes in a Kubernetes environment.
For information about the supported licenses for Kubernetes environments, see Licensing reference for IBM App Connect Operator.
- If you are working in a Kubernetes environment other than IBM Cloud Kubernetes Service, automated route (or ingress) creation is not supported. To expose
your deployed App Connect instances to external traffic, you must
create ingress resources with defined rules to route paths to the internal services and ports. For
more information, see Manually creating ingress definitions for external access to your IBM App Connect instances in Kubernetes environments.
If you are using IBM Cloud Kubernetes Service, you can use the spec.ingress.enabled parameter to enable ingress for each deployed instance and automatically create the required ingress resource. For more information (including the Operator and instance versions that support this feature), see Automatically creating ingress definitions for external access to your IBM App Connect instances on IBM Cloud Kubernetes Service.