From c310b05705ef2f8fe588b8a0ae50de177d65a905 Mon Sep 17 00:00:00 2001 From: David Ashpole Date: Fri, 6 Oct 2017 10:24:11 -0700 Subject: [PATCH] update priority eviction docs --- node/kubelet-eviction.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/node/kubelet-eviction.md b/node/kubelet-eviction.md index 4dd7886..0b627b9 100644 --- a/node/kubelet-eviction.md +++ b/node/kubelet-eviction.md @@ -248,15 +248,12 @@ Priority, and are the largest consumers of the starved resource relative to their scheduling request. It will target pods whose usage of the starved resource exceeds its requests. -Of those pods, it will rank by a function of priority, and usage - requests. -Roughly speaking, if a pod has twice the priority of another pod, it will -recieve half the penalty for usage above requests. If system daemons are -exceeding their allocation (see [Strategy Caveat](strategy-caveat) below), -and all pods are using less than their requests, then it will evict a pod -whose usage is less than requests, based on the function of priority, and -usage - requests. - -Prior to v1.8: +Of those pods, it will rank by priority, then usage - requests. If system +daemons are exceeding their allocation (see [Strategy Caveat](strategy-caveat) below), +and all pods are using less than their requests, then it must evict a pod +whose usage is less than requests, based on priority, then usage - requests. + +Prior to v1.9: The `kubelet` will implement a default eviction strategy oriented around the pod quality of service class.