From 1a681e88ae21c674f5feee7c45d02ab6d95615e7 Mon Sep 17 00:00:00 2001 From: Zoltan Burgermeiszter Date: Tue, 7 Nov 2017 23:27:23 +0000 Subject: [PATCH] LimitRange name fixed in kubectl command (#6133) --- docs/tasks/administer-cluster/memory-constraint-namespace.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/memory-constraint-namespace.md b/docs/tasks/administer-cluster/memory-constraint-namespace.md index 54e40a74c2..f102829dc9 100644 --- a/docs/tasks/administer-cluster/memory-constraint-namespace.md +++ b/docs/tasks/administer-cluster/memory-constraint-namespace.md @@ -49,7 +49,7 @@ kubectl create -f https://k8s.io/docs/tasks/administer-cluster/memory-constraint View detailed information about the LimitRange: ```shell -kubectl get limitrange cpu-min-max-demo --namespace=constraints-mem-example --output=yaml +kubectl get limitrange mem-min-max-demo-lr --namespace=constraints-mem-example --output=yaml ``` The output shows the minimum and maximum memory constraints as expected. But