Skip to content

Commit e6c2e5f

Browse files
committed
Add infrastructure nodes sizing recommendations for 4.6
1 parent aaa756d commit e6c2e5f

File tree

1 file changed

+19
-8
lines changed

1 file changed

+19
-8
lines changed

modules/infrastructure-node-sizing.adoc

Lines changed: 19 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,33 +7,44 @@
77

88
The infrastructure node resource requirements depend on the cluster age, nodes, and objects in the cluster, as these factors can lead to an increase in the number of metrics or time series in Prometheus. The following infrastructure node size recommendations are based on the results of cluster maximums and control plane density focused testing.
99

10-
[options="header",cols="3*"]
10+
[IMPORTANT]
11+
====
12+
The sizing recommendations below are only applicable for the Prometheus, Router, and Registry infrastructure components, which are installed during cluster installation. Logging is a day-two operation and its sizing recommendation are given in the last two columns.
13+
====
14+
15+
[options="header",cols="5*"]
1116
|===
12-
| Number of worker nodes |CPU cores |Memory (GB)
17+
| Number of worker nodes |CPU cores |Memory (GB)|CPU cores with Logging |Memory (GB) with Logging
1318

1419
| 25
1520
| 4
16-
| 32
21+
| 16
22+
| 4
23+
| 64
1724

1825
| 100
1926
| 8
20-
| 64
27+
| 32
28+
| 8
29+
| 128
2130

2231
| 250
23-
| 32
24-
| 192
32+
| 16
33+
| 128
34+
| 16
35+
| 128
2536

2637
| 500
2738
| 32
39+
| 128
40+
| 32
2841
| 192
2942

3043
|===
3144

3245
[IMPORTANT]
3346
====
3447
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 a {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.
35-
36-
The sizing recommendations are applicable only for the infrastructure components which gets installed during the cluster install - Prometheus, Router and Registry. Logging is a day two operation and the recommendations do not take it into account.
3748
====
3849

3950
[NOTE]

0 commit comments

Comments
 (0)