diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-10-06 13:05:39 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-06 13:05:39 -0700 |
| commit | 9979d3736ebd90ea694a0dafb7c659cfabb3fad9 (patch) | |
| tree | 4093368f22e52608ff837315f546346a1ba57555 /hack | |
| parent | aab1ceb21501beef8b692ac265dfc65e8150e354 (diff) | |
| parent | 4b70550e0ea44b3c1e7fd2c8bf7bcfbbb55e3319 (diff) | |
Merge pull request #1162 from dashpole/priority_eviction
Automatic merge from submit-queue.
Update priority eviction docs
After discussion with @dchen1107 and @bsalamat I think it would be simpler to start with a tiered eviction sorting rather than by using a function. See https://github.com/kubernetes/community/pull/846#pullrequestreview-66920328 for some of the rationale.
This PR makes two changes:
1. Changes the release at which changes take effect to 1.9 (since implementation missed 1.8)
2. Changes the strategy from (usage > requests, func(priority, usage - requests)) to (usage > requests, priority, usage - requests)
cc @dchen1107 @derekwaynecarr @vishh
Diffstat (limited to 'hack')
0 files changed, 0 insertions, 0 deletions