openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #22742 from openshift-cherrypick-robot/cherry-pick-22475-to-enterprise-4.5

Browse Source 
[enterprise-4.5] Added 4.5 cluster maximums
This commit is contained in:
Ashley Hardin
2020-06-08 11:24:12 -04:00
committed by GitHub
parent 4f5e9f4bb9 4c46fad06f
commit 5746826210
1 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
modules/openshift-cluster-maximums.adoc
View File

@@ -5,45 +5,51 @@
[id="cluster-maximums_{context}"]
= {product-title} tested cluster maximums
[options="header",cols="5*"]
[options="header",cols="6*"]
|===
| Maximum type |4.1 tested maximum |4.2 tested maximum |4.3 tested maximum |4.4 tested maximum
| Maximum type |4.1 tested maximum |4.2 tested maximum |4.3 tested maximum |4.4 tested maximum |4.5 tested maximum
| Number of Nodes
| 2,000
| 2,000
| 2,000
| 2,000
| 2,000
| Number of Pods footnoteref:[numberofpods,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.]
| 150,000
| 150,000
| 150,000
| 150,000
| 150,000
| 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 footnoteref:[numberofnamepaces, 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.]
| 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 footnoteref:[objectpernamespace,There are
a number of control loops in the system that must iterate over all objects
@@ -55,30 +61,35 @@ the system has enough CPU, memory, and disk to satisfy the application requireme
| 25,000
| 25,000
| 25,000
| 25,000
| Number of Services footnoteref:[servicesandendpoints,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.]
| 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 footnoteref:[objectpernamespace]
| 2,000
| 2,000
| 2,000
| 2,000
| 2,000
|===