From deb2a9c96b003132991696ec0fbeaa66d6cfb019 Mon Sep 17 00:00:00 2001 From: srout Date: Mon, 14 Feb 2022 13:05:33 +0530 Subject: [PATCH] Update memory-default-namespace.md --- .../manage-resources/memory-default-namespace.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md b/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md index 95943edaa5..c19bd465af 100644 --- a/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md +++ b/content/en/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md @@ -16,7 +16,7 @@ A Kubernetes cluster can be divided into namespaces. Once you have a namespace t has a default memory [limit](/docs/concepts/configuration/manage-resources-containers/#requests-and-limits), and you then try to create a Pod with a container that does not specify its own memory -limit its own memory limit, then the +limit, then the {{< glossary_tooltip text="control plane" term_id="control-plane" >}} assigns the default memory limit to that container.