whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Change in Storage Value in Example Scenario (#12831)

Browse Source 
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
This commit is contained in:
sureshpalemoni
2019-03-07 14:42:07 -08:00
committed by Kubernetes Prow Robot
parent b58b88df47
commit 273f3fa713
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/administer-cluster/reserve-compute-resources.md
+1 -1
View File
@@ -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`,