You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: nodes/clusters/nodes-cluster-overcommit.adoc
+17-20Lines changed: 17 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
:context: nodes-cluster-overcommit
2
2
[id="nodes-cluster-overcommit"]
3
-
= Configuring your cluster to place pods on overcommitted nodes
3
+
= Configuring your cluster to place pods on overcommitted nodes
4
4
include::modules/common-attributes.adoc[]
5
5
6
6
toc::[]
@@ -10,29 +10,29 @@ toc::[]
10
10
11
11
12
12
13
-
In an _overcommitted_ state, the sum of the container compute resource requests
13
+
In an _overcommitted_ state, the sum of the container compute resource requests
14
14
and limits exceeds the resources available on the system. For example, you might
15
-
want to use overcommitment in development environments where a trade-off of
16
-
guaranteed performance for capacity is acceptable.
15
+
want to use overcommitment in development environments where a trade-off of
16
+
guaranteed performance for capacity is acceptable.
17
17
18
-
Containers can specify compute resource requests and limits. Requests are used
19
-
for scheduling your container and provide a minimum service guarantee. Limits
18
+
Containers can specify compute resource requests and limits. Requests are used
19
+
for scheduling your container and provide a minimum service guarantee. Limits
20
20
constrain the amount of compute resource that can be consumed on your node.
21
21
22
-
The scheduler attempts to optimize the compute resource use across all nodes
23
-
in your cluster. It places pods onto specific nodes, taking the pods' compute
22
+
The scheduler attempts to optimize the compute resource use across all nodes
23
+
in your cluster. It places pods onto specific nodes, taking the pods' compute
24
24
resource requests and nodes' available capacity into consideration.
25
25
26
26
{product-title} administrators can control the level of overcommit and manage
27
-
container density on nodes. You can configure cluster-level overcommit using
27
+
container density on nodes. You can configure cluster-level overcommit using
28
28
the xref:#nodes-cluster-resource-override_nodes-cluster-overcommit[ClusterResourceOverride Operator]
29
-
to override the ratio between requests and limits set on developer containers.
30
-
In conjunction with xref:#nodes-cluster-node-overcommit_nodes-cluster-overcommit[node overcommit] and
29
+
to override the ratio between requests and limits set on developer containers.
30
+
In conjunction with xref:#nodes-cluster-node-overcommit_nodes-cluster-overcommit[node overcommit] and
31
31
xref:../../applications/deployments/managing-deployment-processes.adoc#deployments-setting-resources_deployment-operations[project memory and CPU limits and defaults], you can adjust the resource limit and request to achieve the desired level of overcommit.
32
32
33
33
[NOTE]
34
34
====
35
-
In {product-title}, you must enable cluster-level overcommit. Node overcommitment is enabled by default.
35
+
In {product-title}, you must enable cluster-level overcommit. Node overcommitment is enabled by default.
36
36
See xref:#nodes-cluster-overcommit-node-disable_nodes-cluster-overcommit[Disabling overcommitment for a node].
37
37
====
38
38
@@ -44,11 +44,11 @@ See xref:#nodes-cluster-overcommit-node-disable_nodes-cluster-overcommit[Disabli
0 commit comments