Hardware requirements and recommendations

Before you install the IBM Cloud Pak for Multicloud Management, review the system requirements for each of the products and the footprint sizing for the entire Cloud Pak.

Red Hat® OpenShift® Container Platform

IBM Cloud Pak for Multicloud Management

Sizing is available for entry, standard, and enterprise footprints.

Notes: A vCPU is equivalent to a Kubernetes compute unit. For more information, see Kubernetes Meaning of CPU Opens in a new tab.

Deployment topology for OpenShift and the IBM Cloud Pak for Multicloud Management

Table 1. Deployment topology configurations for the IBM Cloud Pak for Multicloud Management
Deployment topology Description of usage OpenShift 3.11 node configuration OpenShift node configuration
Development For development, test, and POC Both OpenShift and the Cloud Pak on a single node
Minimal Small cluster deployment

OpenShift:
  1 master node
  1 or 2 infra nodes
  2 or more worker nodes

Cloud Pak:
  1 dedicated worker node (see note)

OpenShift:
  3 master nodes
  2 or more worker nodes

Cloud Pak:
  1 dedicated Cloud Pak worker node

Standard Regular production deployment

OpenShift:
  3 master nodes (native HA)
  2 infra nodes
  4 or more worker nodes

Cloud Pak:
  1 Cloud Pak master node
  1 Cloud Pak management node
  1 Cloud Pak proxy node

OpenShift:
  3 master nodes (native HA)
  4 or more worker nodes

Cloud Pak:
  1 Cloud Pak master node
  1 Cloud Pak management node
  1 Cloud Pak proxy node

Enterprise Medium and large-scale production deployment

OpenShift:
  3 master nodes (native HA)
  2 or more infra nodes
  8 or more worker nodes


Cloud Pak:
  3 Cloud Pak master nodes
  2 Cloud Pak management nodes
  2 Cloud Pak proxy nodes

OpenShift:
  3 master nodes (native HA)
  8 or more worker nodes


Cloud Pak:
  3 Cloud Pak master nodes
  2 Cloud Pak management nodes
  2 Cloud Pak proxy nodes

Note: For one dedicated Cloud Pak worker node, set the master, management, and proxy nodes to one OpenShift worker node.

Default configurations

Table 2. Default configuration sizing
Topology vCPUs Memory Persistent volumes (GB) Disk Space (GB)
Development 8 16 20 100
Minimal 16 32 20 100
Standard 32 60 20 300
Enterprise 54 97 60 700

Note: For the following sizings, requirements are rounded up to the nearest node configuration. All persistent volumes indicated are default. You must size the volumes based on the amount of data that is stored over a time.

Development sizing

Table 3. Development, test, and POC OpenShift node sizing for the IBM Cloud Pak for Multicloud Management
Configuration Number of nodes vCPUs Memory Persistent volumes (GB) Disk Space (GB) Note
master, management, proxy 1 8 16 20 100 The Cloud Pak runs on the same node as OpenShift

Minimal sizing

Table 4. Minimal OpenShift node sizing for the IBM Cloud Pak for Multicloud Management
Configuration Number of nodes vCPUs Memory Persistent volumes (GB) Disk Space (GB)
master, management, proxy 1 16 32 20 100

Standard sizing

Table 5. Standard OpenShift node sizing for the IBM Cloud Pak for Multicloud Management
Configuration Number of nodes vCPUs Memory Persistent volumes (GB) Disk Space (GB)
master 1 16 32 20 100
management 1 12 24 - 100
proxy 1 4 8 - 100

Enterprise sizing

Table 6. Enterprise OpenShift node sizing for the IBM Cloud Pak for Multicloud Management
Configuration Number of nodes vCPUs Memory Persistent volumes (GB) Disk Space (GB)
master 3 48 96 60 200
management 2 24 48 - 200
proxy 2 8 16 - 200

IBM Cloud App Management

Table 7. IBM Cloud Automation Manager sizing
Topology vCPUs Memory Persistent volumes (GB) Resources monitored Max metrics per minute
Development 10 32 75 50 25,000
Minimal 35 55 1,200 3,000 1,000,000
Standard 90 180 7,000 6,000 2,000,000
Enterprise 105 230 10,500 9,000 3,000,000

For more information, see Planning hardware and sizing.

IBM Cloud Automation Manager

Table 8. IBM Cloud App Management sizing
Topology vCPUs Memory Persistent volumes (GB)
Development 12 20 65
Minimal 12 30 65
Standard 15 48 65
Enterprise 18 60 65

For more information, see System requirements.

Sizing for multicluster-endpoint

Table 9. Multicluster-endpoint instructions
Component Name Optional CPU Request CPU Limit Memory Request Memory Limit
ApplicationManager True 100 mCore 500mCore 128 MiB 2 GiB
WorkManager False 100 mCore 500 mCore 128 MiB 512 MiB
ConnectionManager False 100 mCore 500 mCore 128 MiB 256 MiB
ComponentOperator False 50 mCore 250 mCore 128 MiB 512 MiB
CertManager False 100 mCore 300 mCore 100 MiB 300 MiB
PolicyController True 100 mCore 500 mCore 128 MiB 256 MiB
SearchCollector True 25 mCore 250 mCore 128 MiB 512 MiB
ServiceRegistry True 100 mCore 500 mCore 128 MiB 258 MiB
ServiceRegistryDNS True 100 mCore 500 mCore 70 MiB 170 MiB
MeteringSender True 100 mCore 500 mCore 128 MiB 512 MiB
MeteringReader True 100 mCore 500 mCore 128 MiB 512 MiB
MeteringDataManager True 100 mCore 1000 mCore 256 MiB 2560 MiB
MeteringMongoDB True - - 500 MiB 1 GiB
Tiller True - - - -
TopologyWeaveScope(1 per node) True 50 mCore 250 mCore 64 MiB 256 MiB
TopologyWeaveApp True 50 mCore 250 mCore 128 MiB 256 MiB
TopologyCollector True 50 mCore 100 mCore 20 MiB 50 MiB
MulticlusterEndpointOperator False 100 mCore 500 mCore 100 MiB 500 MiB

Sizing for management hub services

Table 10. Hub services sizing
Service Name Optional CPU Request CPU Limit Memory Request Memory Limit Persistent Volume (value is default) Additional considerations
Catalog-ui, Common-web-ui, iam-policy-controller, key-management, mcm-kui, metering, monitoring, multicluster-hub,nginx-ingress, search Default 9,025 m 29,289 m 16,857 Mi 56,963 Mi 20 GiB
Audit Logging Optional 125 m 500 m 250 Mi 700 Mi
CIS Policy Controller Optional 525 m 1,450 m 832 Mi 2,560 Mi
Image Security Enforcement Optional 128 m 256 m 128 Mi 256 Mi
Licensing Optional 200 m 500 m 256 Mi 512 Mi
Logging Optional 1,500 m 3,000 m 9,940 Mi 10,516 Mi 20 GiB
Multitenancy Account Quota Enforcement Optional 25 m 100 m 64 Mi 64 Mi
Mutation Advisor Optional 1,000 m 3,300 m 2,052 Mi 7,084 Mi 100 GiB
Notary Optional 600 m 600 m 1,024 Mi 1,024 Mi
Secret Encryption Policy Controller Optional 50 m 100 m 100 Mi 200 Mi 110 GiB
Secure Token Service (STS) Optional 410 m 600 m 94 Mi 314 Mi Requires Red Hat OpenShift Service Mesh (Istio)
System Healthcheck Service Optional 75 m 600 m 96 Mi 256 Mi
Vulnerability Advisor (VA) Optional 1,940 m 4,440 m 8,040 Mi 27,776 Mi 10 GiB Requires Red Hat OpenShift logging (Elasticsearch)