From 528fd25b3f702c3c477b87997680e08186cf2bb5 Mon Sep 17 00:00:00 2001 From: Pingan Date: Wed, 12 Jun 2019 21:53:34 +0800 Subject: [PATCH] fix a mistake in limit-range.md (#14836) --- content/en/docs/concepts/policy/limit-range.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/policy/limit-range.md b/content/en/docs/concepts/policy/limit-range.md index 97b70358a1..1ab6073fe3 100644 --- a/content/en/docs/concepts/policy/limit-range.md +++ b/content/en/docs/concepts/policy/limit-range.md @@ -179,7 +179,7 @@ kubectl get po/busybox1 -n limitrange-demo -o json | jq ".spec.containers[2].re ``` - The `busybox-cnt03` Container inside `busybox1` Pod defined `limits.cpu=500m` and `limits.memory=200Mi` but no `requests` for cpu and memory. -- The container do not define a request section, the defaultRequest defined in the limit-mem-cpu-per-container LimitRange is not used to fill its limits section but the limits defined by the container are set as requests `limits.cpu=500m` and `limits.memory=900Mi`. +- The container do not define a request section, the defaultRequest defined in the limit-mem-cpu-per-container LimitRange is not used to fill its limits section but the limits defined by the container are set as requests `limits.cpu=500m` and `limits.memory=200Mi`. - `100m <= 500m <= 800m` , The container cpu limit (500m) falls inside the authorized CPU limit range. - `99Mi <= 200Mi <= 1Gi` , The container memory limit (200Mi) falls inside the authorized Memory limit range. - No request/limits ratio set , thus the container is valid and created.