From b189eebd48590061fa9298180e17ac6bb53e8b67 Mon Sep 17 00:00:00 2001 From: Tamilselvan Date: Wed, 31 May 2023 10:40:25 +0530 Subject: [PATCH] wrapping in to <80 characters --- .../manage-resources-containers.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/content/en/docs/concepts/configuration/manage-resources-containers.md b/content/en/docs/concepts/configuration/manage-resources-containers.md index 309f716067..45686178d6 100644 --- a/content/en/docs/concepts/configuration/manage-resources-containers.md +++ b/content/en/docs/concepts/configuration/manage-resources-containers.md @@ -11,17 +11,16 @@ feature: -When you specify a {{< glossary_tooltip term_id="pod" >}}, you can optionally specify how -much of each resource a {{< glossary_tooltip text="container" term_id="container" >}} needs. -The most common resources to specify are CPU and memory (RAM); there are others. +When you specify a {{< glossary_tooltip term_id="pod" >}}, you can optionally specify how much of each resource a +{{< glossary_tooltip text="container" term_id="container" >}} needs. The most common resources to specify are CPU and memory +(RAM); there are others. When you specify the resource _request_ for containers in a Pod, the -{{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}} uses this -information to decide which node to place the Pod on. When you specify a resource _limit_ -for a container, the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} enforces those limits so that the running container is not -allowed to use more of that resource than the limit you set. The kubelet also reserves -at least the _request_ amount of that system resource specifically for that container -to use. +{{< glossary_tooltip text="kube-scheduler" term_id="kube-scheduler" >}} uses this information to decide which node to place the Pod on. +When you specify a resource _limit_ for a container, the {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} enforces those +limits so that the running container is not allowed to use more of that resource +than the limit you set. The kubelet also reserves at least the _request_ amount of +that system resource specifically for that container to use.