Supported platforms
Learn about which Red Hat OpenShift Container Platform versions and public cloud platforms are supported for IBM Cloud Pak® for AIOps and Infrastructure Automation.
Red Hat OpenShift Container Platform
IBM Cloud Pak for AIOps and Infrastructure Automation adhere to the IBM Cloud Pak and Red Hat OpenShift version compatibility objective, and support and recommend installing on a supported Red Hat OpenShift EUS minor version.
For more information about support timelines for Red Hat OpenShift, including when a specific version is going out of support, see the Red Hat OpenShift Container Platform Life-Cycle Policy in the Red Hat OpenShift documentation.
Deployment | Platform | Red Hat OpenShift Container Platform version |
---|---|---|
IBM Cloud Pak for AIOps | Linux x86_64 | 4.12 (minimum 4.12.50) 4.13 (minimum 4.13.34) 4.14 4.15 |
Infrastructure Automation (installed with IBM Cloud Pak for AIOps) | Linux x86_64 | 4.12 (minimum 4.12.50) 4.13 (minimum 4.13.34) 4.14 4.15 |
Infrastructure Automation (installed stand-alone) | Linux on Power (ppc64le) (non-FIPs) Linux® on IBM Z® and LinuxONE (s390x) |
4.12 (minimum 4.12.50) 4.13 (minimum 4.13.34) 4.14 4.15 |
Important:
- If you are planning to upgrade Red Hat OpenShift as part of an upgrade to IBM Cloud Pak for AIOps or Infrastructure Automation 4.6.1, you must complete the IBM Cloud Pak for AIOps or Infrastructure Automation upgrade before you upgrade Red Hat OpenShift.
- The hardware architecture for installing IBM Cloud Pak for AIOps must be x86_64 (amd64).
- Red Hat OpenShift v4.14 and onwards support heterogeneous architectures, but IBM Cloud Pak for AIOps and Infrastructure Automation do not support heterogeneous architectures. All nodes in the Red Hat OpenShift cluster must have the same architecture.
- If you are installing Infrastructure Automation on Linux on Power (ppc64le) with FIPS enabled, see the following known issue: Infrastructure Automation install fails on FIPS enabled Power cluster
Red Hat OpenShift installation mode
IBM Cloud Pak for AIOps and Infrastructure Automation both support the OpenShift OwnNamespace
and AllNamespaces
installation modes. The OwnNamespace
installation mode is the recommended installation mode
because it provides better resilience and performance.
In the OwnNamespace
installation mode, you must create and select a project (namespace) for the IBM Cloud Pak for AIOps or Infrastructure Automation operator to be installed into. In this mode, the operator watches and is available
for use only in this single namespace. The All namespaces on the cluster (default)
installation mode in the UI installation of the IBM Cloud Pak for AIOps or Infrastructure Automation operator is equivalent to the AllNamespaces
mode in the CLI installation. In this mode, the operator is installed in the openshift-operators
project (namespace), and watches and is available to all namespaces in the cluster. The Operator Deployment Lifecycle Manager (ODLM)
installs suboperators in the same project (namespace) that you created the Installation
custom resource instance in. Each suboperator watches and is available for use in its project (namespace).
For more information on Red Hat OpenShift operator installation modes, see Operator groups in the Red Hat OpenShift Container Platform documentation.
Note: If you install IBM Cloud Pak for AIOps and Infrastructure Automation, then they must use the same installation mode.
Resource allocation for nodes
Red Hat OpenShift nodes must have adequate resources reserved. For more information, see Allocating resources for nodes in an OpenShift Container Platform cluster in the Red Hat OpenShift documentation, and the Red Hat Customer Portal.
Linux
Technology preview feature: you can install a nonproduction IBM Cloud Pak for AIOps deployment directly on Linux, without the need to install Red Hat OpenShift. For more information, see Installing IBM Cloud Pak for AIOps on Linux.
Cloud platforms
For more information about the storage providers that you can use on the following platforms, see Recommended storage providers.
IBM Cloud
You can install IBM Cloud Pak for AIOps and Infrastructure Automation on IBM Cloud® with:
- Red Hat OpenShift
- Red Hat® OpenShift® on IBM Cloud® service (ROKS). For more information about ROKS, see the Red Hat OpenShift documentation Red Hat OpenShift on IBM Cloud
.
For more information about installing IBM Cloud Pak for AIOps on ROKS, see Installing IBM Cloud Pak for AIOps on ROKS.
AWS Marketplace
You can install IBM Cloud Pak for AIOps and Infrastructure Automation on AWS with:
- Red Hat® OpenShift®
- Red Hat OpenShift Service on AWS (ROSA). For more information about ROSA, see the Red Hat documentation Red Hat OpenShift Service on AWS
.
For more information about installing IBM Cloud Pak for AIOps on ROSA, see Installing IBM Cloud Pak for AIOps on ROSA.
AWS GovCloud
You can install IBM Cloud Pak for AIOps on AWS GovCloud. Infrastructure Automation is not supported on AWS GovCloud.
For more information about installing IBM Cloud Pak for AIOps on AWS into a government region, see Installing IBM Cloud Pak for AIOps on AWS GovCloud.
Microsoft® Azure
You can install IBM Cloud Pak for AIOps and Infrastructure Automation on Azure with:
-
Red Hat OpenShift
-
Azure Red Hat OpenShift (ARO). For more information about ARO, see the Microsoft documentation Azure Red Hat OpenShift
.
For more information about installing IBM Cloud Pak for AIOps on (ARO), see Installing IBM Cloud Pak for AIOps on ARO.
Google Cloud Platform (GCP)
You can install IBM Cloud Pak for AIOps on GCP with Red Hat OpenShift. Infrastructure Automation is not supported on GCP.
For more information about IBM Cloud Pak for AIOps on GCP, see Installing IBM Cloud Pak for AIOps on GCP.