diff options
| author | David Ashpole <dashpole@google.com> | 2017-10-06 10:24:11 -0700 |
|---|---|---|
| committer | David Ashpole <dashpole@google.com> | 2017-10-06 10:24:11 -0700 |
| commit | 4b70550e0ea44b3c1e7fd2c8bf7bcfbbb55e3319 (patch) | |
| tree | e2e9f9f0c83368d9cabf4a132c39bcf06e1065d2 | |
| parent | ff82a64245cc88cd1b8828b8e7cd001008770415 (diff) | |
update priority eviction docs
| -rw-r--r-- | contributors/design-proposals/node/kubelet-eviction.md | 15 |
1 files changed, 6 insertions, 9 deletions
diff --git a/contributors/design-proposals/node/kubelet-eviction.md b/contributors/design-proposals/node/kubelet-eviction.md index 4dd78861..0b627b97 100644 --- a/contributors/design-proposals/node/kubelet-eviction.md +++ b/contributors/design-proposals/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. |
