From 2bee076fb8122310e4dfe0a78b85e0d09948e936 Mon Sep 17 00:00:00 2001 From: Joao Luna Date: Tue, 19 May 2020 21:14:28 +0100 Subject: [PATCH] Revert "Small typo in pod-overhead.md" This reverts commit 2b0e08adc744bf3519a4e286be0c2af58057c4a7. --- content/en/docs/concepts/configuration/pod-overhead.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/pod-overhead.md b/content/en/docs/concepts/configuration/pod-overhead.md index ad14817c49..9661264820 100644 --- a/content/en/docs/concepts/configuration/pod-overhead.md +++ b/content/en/docs/concepts/configuration/pod-overhead.md @@ -113,7 +113,7 @@ requests and the overhead, then looks for a node that has 2.25 CPU and 320 MiB o Once a Pod is scheduled to a node, the kubelet on that node creates a new {{< glossary_tooltip text="cgroup" term_id="cgroup" >}} for the Pod. It is within this pod that the underlying container runtime will create containers. -If the resource has a limit defined for each container (Guaranteed QoS or Burstable QoS with limits defined), +If the resource has a limit defined for each container (Guaranteed QoS or Bustrable QoS with limits defined), the kubelet will set an upper limit for the pod cgroup associated with that resource (cpu.cfs_quota_us for CPU and memory.limit_in_bytes memory). This upper limit is based on the sum of the container limits plus the `overhead` defined in the PodSpec.