Skip to content

Commit 738dc6b

Browse files
committed
Update Infrastructure sizing table and note
Signed-off-by: Raul Sevilla <[email protected]>
1 parent fdf7124 commit 738dc6b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

modules/infrastructure-node-sizing.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ _Infrastructure nodes_ are nodes that are labeled to run pieces of the {product-
1111
|===
1212
| Number of worker nodes |Cluster density, or number of namespaces |CPU cores |Memory (GB)
1313

14-
| 25
14+
| 27
1515
| 500
1616
| 4
17-
| 48
17+
| 24
1818

19-
| 100
19+
| 120
2020
| 1000
2121
| 8
22-
| 96
22+
| 48
2323

2424
| 252
2525
| 4000
@@ -37,9 +37,9 @@ In general, three infrastructure nodes are recommended per cluster.
3737

3838
[IMPORTANT]
3939
====
40-
These sizing recommendations are based on scale tests, which create a large number of objects across the cluster. These tests include reaching some of the cluster maximums. In the case of 250 and 500 node counts on an {product-title} {product-version} cluster, these maximums are 10000 namespaces with 61000 pods, 10000 deployments, 181000 secrets, 400 config maps, and so on. Prometheus is a highly memory intensive application; the resource usage depends on various factors including the number of nodes, objects, the Prometheus metrics scraping interval, metrics or time series, and the age of the cluster. The disk size also depends on the retention period. You must take these factors into consideration and size them accordingly.
40+
These sizing recommendations should be used as a guideline. Prometheus is a highly memory intensive application; the resource usage depends on various factors including the number of nodes, objects, the Prometheus metrics scraping interval, metrics or time series, and the age of the cluster. In addition, the router resource usage can also be affected by the number of routes and the amount/type of inbound requests.
4141
42-
These sizing recommendations are only applicable for the Prometheus, Router, and Registry infrastructure components, which are installed during cluster installation. Logging is a day-two operation and is not included in these recommendations.
42+
These recommendations apply only to infrastructure nodes hosting Monitoring, Ingress and Registry infrastructure components installed during cluster creation.
4343
====
4444

4545
[NOTE]

0 commit comments

Comments
 (0)