From 273f3fa7130a7b31424cdc6f58e7cbd5769bf5e3 Mon Sep 17 00:00:00 2001 From: sureshpalemoni Date: Thu, 7 Mar 2019 14:42:07 -0800 Subject: [PATCH] Change in Storage Value in Example Scenario (#12831) In the calculation of this `Allocatable` will be `14.5 CPUs`, `28.5Gi` of memory and `88Gi` of local storage. - It was 98Gi for storage instead of 88Gi which is derived after negating System-Reserved+Kube-reserved+eviction+hard --- .../docs/tasks/administer-cluster/reserve-compute-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md index 923db9a03c..2cd6afa304 100644 --- a/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md +++ b/content/en/docs/tasks/administer-cluster/reserve-compute-resources.md @@ -211,7 +211,7 @@ Here is an example to illustrate Node Allocatable computation: * `--eviction-hard` is set to `memory.available<500Mi,nodefs.available<10%` Under this scenario, `Allocatable` will be `14.5 CPUs`, `28.5Gi` of memory and -`98Gi` of local storage. +`88Gi` of local storage. Scheduler ensures that the total memory `requests` across all pods on this node does not exceed `28.5Gi` and storage doesn't exceed `88Gi`. Kubelet evicts pods whenever the overall memory usage across pods exceeds `28.5Gi`,