Skip to content

Commit 230d1da

Browse files
authored
Merge pull request #29610 from chaitanyaenr/disk_throttling
Add recommendation around disk throughput impacting runtime
2 parents bbb3a2f + 6230ed6 commit 230d1da

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

modules/recommended-node-host-practices.adoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,14 @@ actual container starting. Therefore, a system running 10 pods will actually
2727
have 20 containers running.
2828
====
2929

30+
[NOTE]
31+
====
32+
Disk IOPS throttling from the cloud provider might have an impact on CRI-O and kubelet.
33+
They might get overloaded when there are large number of I/O intensive pods running on
34+
the nodes. It is recommended that you monitor the disk I/O on the nodes and use volumes
35+
with sufficient throughput for the workload.
36+
====
37+
3038
`podsPerCore` sets the number of pods the node can run based on the number of
3139
processor cores on the node. For example, if `podsPerCore` is set to `10` on a
3240
node with 4 processor cores, the maximum number of pods allowed on the node will

0 commit comments

Comments
 (0)