Skip to content

Commit 5cc79b9

Browse files
authored
Update k8s-best-practices-requests-limits.adoc
1 parent 06cf046 commit 5cc79b9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Memory Limits Cause OOMKills
2424
* Difficult to predict worst-case memory usage for infrastructure components.
2525
* Can result in crash loops, degraded service, and unrecoverable clusters.
2626
27-
Why Limits are a Problem for Cluster Components
27+
*Why Limits are a Problem for Cluster Components*
2828

2929
Unlike with user workloads, setting resource limits for cluster components presents several challenges and is strongly discouraged:
3030

@@ -36,14 +36,14 @@ Therefore, *cluster components SHOULD NOT be configured with resource limits*.
3636

3737
However, *cluster components MUST declare resource requests for both CPU and memory*.
3838

39-
==== Benefits of Using Requests Without Limits
39+
*Benefits of Using Requests Without Limits*
4040

4141
* *Guaranteed Minimums and Bursting*: Specifying requests without limits ensures components receive their required minimum resources and can burst when needed.
4242
* *Balancing Efficiency and Performance*: When setting resource requests:
4343
** If too low, the component may be starved under load, leading to degraded performance and service.
4444
** If too high, the scheduler may be unable to place the component, leading to crash loops or failed deployments. Excessively high requests can also starve user workloads, particularly in small or single-node clusters.
4545
46-
== Resource Requests: Compressible vs Incompressible
46+
*Resource Requests: Compressible vs Incompressible*
4747

4848
Kubernetes treats resources differently depending on their behavior under pressure:
4949

@@ -54,14 +54,14 @@ Kubernetes treats resources differently depending on their behavior under pressu
5454
|Incompressible |Fails without required amount |Memory, storage
5555
|===
5656

57-
=== Requesting Resources
57+
*Requesting Resources*
5858

5959
* *Compressible (e.g., CPU)*: Requests should be balanced to ensure proportional system behavior and fairness.
6060
* *Incompressible (e.g., memory)*: Requests should reflect minimum safe usage to avoid runtime failure.
6161
6262
See: link:https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#resource-units-in-kubernetes[More details on setting requests for different resource types]
6363

64-
== Alternatives to Resource Limits
64+
*Alternatives to Resource Limits*
6565

6666
Although limits are generally avoided for cluster components, the following mechanisms can help manage resources and prioritize workloads:
6767

0 commit comments

Comments
 (0)