Hardware requirements and recommendations

Review the minimum CPU, Memory, RAM, and disk space requirements for setting up and running IBM® Cloud Private clusters.

The following tables list the minimum system requirements per node for running IBM Cloud Private in both evaluation and production environments.

System requirements vary depending on whether you want to set up a multi-node cluster, or set up a test environment by using a single host. A single host environment has boot, master, worker, and proxy nodes all running on a single host.

Hardware requirements (single node cluster)

Table 1. Minimum hardware requirements for a single node cluster
Requirement All management services enabled Metering and monitoring services disabled Notes
Number of hosts 1 1
Cores 10 or more 4 or more Choose a modern processor with multiple cores. Servers often come packaged with two sockets (two processors), so the total number of cores in the system is the number of sockets multiplied by the number of cores in each processor. Today, processors typically have at least eight cores per processor. Higher end processors can have 20 or more cores per processor. When it comes to choosing a processor, it might be of best value to take a moderate approach. That is, select a processor that has an average (not the highest or the lowest) number of cores, frequency, and cache size.
CPU >=2.4 GHz >=2.4 GHz
  • For a Linux® 64-bit cluster, choose a CPU that supports SSE 4.2.
  • For a Linux® on Power® 64-bit LE cluster, use a CPU that is version Power8 or higher.
RAM 20 GB or more 8 GB or more You might need more than this minimum amount of memory, if you plan to run applications in this test cluster that might use a substantial amount of memory.
Disk space to install >=200 GB >=151 GB

Hardware requirements (multi-node cluster)

Note: In your multi-node cluster, if you do not use a management node, ensure that the master node meets the requirements of the management node plus the master node.

Requirement Boot node Master node Proxy node Worker node Management node VA node Notes
Number of hosts 1 1, 3, or 5 1 or more 1 or more 1 or more 1, 3, or 5
Cores 1 or more 2 or more 2 or more 1 or more 4 or more
  • 2 or more
  • 6 or more (production environment)
Choose a modern processor with multiple cores. Servers often come packaged with two sockets (two processors), so the total number of cores in the system is the number of sockets, multiplied by the number of cores in each processor. Today, processors typically have at least eight cores per processor. Higher end processors can have 20 or more cores per processor. When it comes to choosing a processor, you might select one that has not the highest or the lowest number of cores, frequency, and cache size.
CPU >= 2.4 GHz >= 2.4 GHz >= 2.4 GHz >= 2.4 GHz >= 2.4 GHz >= 2.4 GHz
  • For a Linux® 64-bit cluster, choose a CPU that supports SSE 4.2.
  • For a Linux® on Power® 64-bit LE cluster, use a CPU that is version Power8 or higher.
  • For a Linux on IBM® Z cluster, use a CPU that is version EC12 or higher.
RAM >=4 GB >=4 GB >=4 GB >=4 GB >=8 GB
  • >=8 GB
  • >=16 GB (production environment)
Disk space to install >=100 GB >=151 GB >=40 GB >=100 GB >=100 GB
  • >=100 GB
  • >=400 GB (production environment)

Note: Accounts that use PowerVM can share cores. For larger environments, assign processor cores.

Disk space requirements

Location Minimum disk space Node
/var/lib/docker >40 GB All Nodes
/var/lib/etcd >1 GB Master
/var/lib/registry Must be large enough to host the Docker images that you plan to host in your private image registry Master
/opt/ibm/cfc/ >100 GB Master and Management
/var/lib/kubelet >10 GB
  • All Nodes need >10 GB of disk space
  • If you enable the Vulnerability Advisor, the VA node needs >100 GB of disk space.
/var/lib/icp/va/ >100 GB VA node

Important: The /var directory is the default storage location for most Docker images and the containers that are used in your IBM Cloud Private cluster.

To prevent disk space issues, mount the default storage directories on separate paths that have larger disk capacities. For more information about mounting the Docker storage directory (/var/lib/docker), see Specifying a default Docker storage directory by using bind mount. You can also use this bind method to mount the other IBM Cloud Private default storage directories. To prevent disk space issues in your cluster, you might want to use a bind mount to mount the following directories:

For more information about mounting the default storage directories, see Specifying other default storage directories by using bind mount.

File system requirements

For a list of file systems that are supported by IBM Cloud Private, see Supported file systems and storage.

The required file systems table documents the file system types that are required in IBM Cloud Private but are not supported by IBM Cloud Private.

Table 2. Required file systems
File system type Version Notes
POSIX-compliant shared file system Not applicable In high availability (HA) clusters, you must set up a POSIX-compliant file system for shared storage. This file system must be located outside of your IBM Cloud Private cluster. See High availability IBM® Cloud Private clusters.

Supported IaaS and hypervisors

IBM Cloud Private is certified on several Infrastructure as a Service (IaaS) providers and hypervisors.

Table 1. Supported IaaS versions
IaaS Versions
VMware vCenter 6.5
OpenStack Mitaka and later
Hyper-V 10.0.15063.0 and later
IBM PowerVC 1.4.1 and later

IBM Cloud Private is certified on KVM, ESX, and IBM PowerVM hypervisors.

IBM Cloud Private can also run on the IBM Cloud and Amazon Web Services (AWS) cloud platforms.

Kubernetes and Cloud Foundry demonstrated portability across multiple IaaS providers in the community. While IBM Cloud Private is certified for on-premises installations on VMWare, OpenStack, and bare metal, you can install it on other IaaS systems. For additional information, contact your sales representative.