9.2. OpenShift Container Platform tested cluster maximums

Maximum type4.1 tested maximum4.2 tested maximum4.3 tested maximum4.4 tested maximum4.5 tested maximum

Number of nodes

2,000

2,000

2,000

250

500

Number of pods [1]

150,000

150,000

150,000

62,500

62,500

Number of pods per node

250

250

500

500

500

Number of pods per core

There is no default value.

There is no default value.

There is no default value.

There is no default value.

There is no default value.

Number of namespaces [2]

10,000

10,000

10,000

10,000

10,000

Number of builds

10,000 (Default pod RAM 512 Mi) - Pipeline Strategy

10,000 (Default pod RAM 512 Mi) - Pipeline Strategy

10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy

10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy

10,000 (Default pod RAM 512 Mi) - Source-to-Image (S2I) build strategy

Number of pods per namespace [3]

25,000

25,000

25,000

25,000

25,000

Number of services [4]

10,000

10,000

10,000

10,000

10,000

Number of services per namespace

5,000

5,000

5,000

5,000

5,000

Number of back ends per service

5,000

5,000

5,000

5,000

5,000

Number of deployments per namespace [3]

2,000

2,000

2,000

2,000

2,000

  1. The pod count displayed here is the number of test pods. The actual number of pods depends on the application’s memory, CPU, and storage requirements.
  2. When there are a large number of active projects, etcd might suffer from poor performance if the keyspace grows excessively large and exceeds the space quota. Periodic maintenance of etcd, including defragmentaion, is highly recommended to free etcd storage.
  3. There are a number of control loops in the system that must iterate over all objects in a given namespace as a reaction to some changes in state. Having a large number of objects of a given type in a single namespace can make those loops expensive and slow down processing given state changes. The limit assumes that the system has enough CPU, memory, and disk to satisfy the application requirements.
  4. Each service port and each service back end has a corresponding entry in iptables. The number of back ends of a given service impact the size of the endpoints objects, which impacts the size of data that is being sent all over the system.