Supported platforms

Red Hat OpenShift Container Platform

Infrastructure Automation adheres 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.

Important:

• If you are planning to upgrade Red Hat OpenShift as part of an upgrade to Infrastructure Automation 4.8.1, you must complete the Infrastructure Automation upgrade before you upgrade Red Hat OpenShift.
• The hardware architecture for installing IBM Cloud Pak for AIOps must be x86_64 (amd64). For more information about hardware requirements for IBM Cloud Pak for AIOps, see IBM Cloud Pak for AIOps: Supported hardware.
• Red Hat OpenShift v4.14 and onwards support heterogeneous architectures, but Infrastructure Automation does 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

Infrastructure Automation supports 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 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 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.

Cloud platforms

For more information about the storage providers that you can use on the following platforms, see Recommended storage providers.

• IBM Cloud®
• AWS Marketplace
• Microsoft® Azure