From 3cf47e9bb038b3c12af609a4cb3e8c112b443e7e Mon Sep 17 00:00:00 2001 From: tamilselvan1102 Date: Thu, 25 May 2023 17:28:45 +0530 Subject: [PATCH] Add glossary tooltip for kubelet --- .../docs/concepts/configuration/manage-resources-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/manage-resources-containers.md b/content/en/docs/concepts/configuration/manage-resources-containers.md index f7d2d1d8e28f1..309f716067576 100644 --- a/content/en/docs/concepts/configuration/manage-resources-containers.md +++ b/content/en/docs/concepts/configuration/manage-resources-containers.md @@ -18,7 +18,7 @@ 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 kubelet enforces those limits so that the running container is not +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.