Skip to content

Commit 8f33678

Browse files
authored
Update k8s-best-practices-requests-limits.adoc
1 parent 94d61b2 commit 8f33678

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

modules/k8s-best-practices-requests-limits.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,4 +76,8 @@ Although limits are generally avoided for cluster components, the following mech
7676

7777
Nodes can be overcommitted, influencing how requests and limits are applied.
7878

79-
* Overcommitted clusters often experience pod kills and kubelet restarts, degrading the product exp*
79+
* Overcommitted clusters often experience pod kills and kubelet restarts, degrading the product experience and increasing support costs.
80+
* Use quotas to enforce guaranteed capacity in production.
81+
* In development, overcommitment may be acceptable where performance trade-offs are tolerable.
82+
83+
See: link:https://docs.openshift.com/container-platform/latest/nodes/scheduling/nodes-scheduler-overcommit.html[Configuring your cluster to place pods on overcommitted nodes]

0 commit comments

Comments
 (0)