From 2934358f13c4f1f6267bd0733b69c6470e8776af Mon Sep 17 00:00:00 2001 From: "Eric Mountain @ Amadeus" Date: Mon, 31 Jul 2017 12:01:58 +0200 Subject: [PATCH] Minor fix in example resource limit policy Looks like ``` the cluster operator may want to set limits that a pod must consume at least 20% of the memory and CPU ``` was meant to be ``` the cluster operator may want to set limits that a pod must consume no more than 20% of the memory and CPU ``` --- docs/tasks/administer-cluster/cpu-memory-limit.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/cpu-memory-limit.md b/docs/tasks/administer-cluster/cpu-memory-limit.md index c6207c9ed9..10224c02c3 100644 --- a/docs/tasks/administer-cluster/cpu-memory-limit.md +++ b/docs/tasks/administer-cluster/cpu-memory-limit.md @@ -210,8 +210,8 @@ to 512MB of memory. The cluster operator creates a separate namespace for each each namespace. 3. Users may create a pod which consumes resources just below the capacity of a machine. The left over space may be too small to be useful, but big enough for the waste to be costly over the entire cluster. As a result, -the cluster operator may want to set limits that a pod must consume at least 20% of the memory and CPU of their -average node size in order to provide for more uniform scheduling and limit waste. +the cluster operator may want to set limits that a pod must consume no more than 20% of the memory and CPU of +their average node size in order to provide for more uniform scheduling and limit waste. ## Summary