Chapter 3. Supported Infrastructure and Platforms

Red Hat OpenShift Container Storage supports deployment on Red Hat OpenShift Container Platform deployed with Installer Provisioned Infrastructure (Full Stack Automation) and User Provisioned Infrastructure (Pre Existing Infrastructure).

  • Installer Provisioned Infrastructure (IPI)

    With full stack automation, the installer controls all areas of the installation including infrastructure provisioning with an opinionated best practices deployment on Red Hat OpenShift Container Platform.

  • User Provisioned Infrastructure (UPI))

    With pre-existing infrastructure deployments, administrators are responsible for creating and managing their own infrastructure allowing greater customization and operational flexibility.

Red Hat OpenShift Container Storage supports deployment on the following infrastructures:

Table 3.1. Minimum infrastructure requirements

InfrastructureDeployment typeRequirements

Amazon Web Services

IPI, UPI

Amazon EC2 with a minimum instance type m5.4xlarge

VMware

UPI

vSphere 6.7 Update 2 and higher with vSAN or VMFS datastore.

See VMware vSphere infrastructure requirements for details.

3.1. Node requirements

The requirements mentioned in the section apply to pre-existing Red Hat OpenShift Container Platform deployments only and are required for exclusive use by Red Hat OpenShift Container Storage.

A minimum of 3 nodes are required for deployment with at least one Object Storage Daemon (OSD) and one Monitor daemon (MON) on each node.

Table 3.2. Minimum requirements for each starting node

ComponentsRequirements

CPU

16

Memory

64  GB

Disk

2 TiB storage per disk (1 disk by default; scalable to 3 disks per node)

Maintain uniform disk sizes across nodes for storage disks.

MON

10 GiB storage per MON on all the storage nodes.

  • In case a node with MON fails and the MON failover to a new node, 10 GiB space will then be consumed on the new node as well.

Note: At a time only 3 nodes require the storage space.

Note
  • In case you plan to run any other workload on a storage node, you must add additional resources (CPU/Memory/Space).
  • In this section, 1 CPU Unit maps to the Kubernetes concept of 1 CPU unit. For more information, see CPU units.

    • 1 unit of CPU is equivalent to 1 core for non-hyperthreaded CPUs.
    • 2 units of CPU are equivalent to 1 core for hyperthreaded CPUs.
    • Red Hat OpenShift Container Storage core-based subscriptions always come in pairs (2 cores).

      Example: For a 3 node cluster, a minimum of 3 x 16 = 48 units of CPU are required. 48 units of CPU are equivalent to 24 cores which is equivalent to 12 quantity of Red Hat OpenShift Container Storage (2 core) subscriptions.

3.2. Storage class requirements

Red Hat OpenShift Container Storage makes use of the OpenShift Container Platform default storage class, and expects a certain default storage class depending on your infrastructure provider.

These classes are configured on OpenShift Container Platform nodes automatically, but if your OpenShift Container Platform node uses a different storage class as the default, you must change the default storage class back to the appropriate storage class for your infrastructure provider.

  • On Amazon Web Services, the default storage class must be gp2.
  • On VMware vSphere, the default storage class must be thin.

3.3. Software requirements

Red Hat OpenShift Container Storage 4.2 is supported on Red Hat OpenShift Container Platform 4.2.13 and later versions.

For more information, see Red Hat OpenShift Container Storage and Red Hat OpenShift Container Platform interoperability matrix.

Important

OpenShift Container Platform must not be installed or running with Federal Information Processing Standards (FIPS) mode enabled.

Nodes that run only storage workloads require a subscription for Red Hat OpenShift Container Storage. Nodes that run other workloads in addition to storage workloads require both Red Hat OpenShift Container Storage and Red Hat OpenShift Container Platform subscriptions.