From a191d716276b9fb951b1f99e2380c4c626396edd Mon Sep 17 00:00:00 2001 From: srout Date: Mon, 14 Feb 2022 12:37:58 +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 ff2a4082c2..95943edaa5 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 @@ -13,7 +13,7 @@ This page shows how to configure default memory requests and limits for a {{< glossary_tooltip text="namespace" term_id="namespace" >}}. A Kubernetes cluster can be divided into namespaces. Once you have a namespace that -that has a default memory +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