Merge pull request #22217 from davidopp/rescheduling

Automatic merge from submit-queue [WIP/RFC] Rescheduling in Kubernetes design proposal Proposal by @bgrant0607 and @davidopp (and inspired by years of discussion and experience from folks who worked on Borg and Omega). This doc is a proposal for a set of inter-related concepts related to "rescheduling" -- that is, "moving" an already-running pod to a new node in order to improve where it is running. (Specific concepts discussed are priority, preemption, disruption budget, quota, `/evict` subresource, and rescheduler.) Feedback on the proposal is very welcome. For now, please stick to comments about the design, not spelling, punctuation, grammar, broken links, etc., so we can keep the doc uncluttered enough to make it easy for folks to comment on the more important things. ref/ #22054 #18724 #19080 #12611 #20699 #17393 #12140 #22212 @HaiyangDING @mqliang @derekwaynecarr @kubernetes/sig-scheduling @kubernetes/huawei @timothysc @mml @dchen1107

Merge pull request #22217 from davidopp/rescheduling
710374b6 · k8s-merge-robot · GitHub · 00d00cda · b77e3929 · 710374b6
Commit 710374b6 authored Jul 10, 2016 by k8s-merge-robot Committed by GitHub Jul 10, 2016
Expand all Show whitespace changes
Inline Side-by-side

Showing with 2 additions and 0 deletions

CHANGELOG.md CHANGELOG.md +2 -0

rescheduling.md docs/proposals/rescheduling.md +0 -0

No files found.
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,8 @@
  - [Downloads](#downloads)
  - [Highlights](#highlights)
  - [Known Issues and Important Steps before Upgrading](#known-issues-and-important-steps-before-upgrading)
+      - [ThirdPartyResource](#thirdpartyresource)
+      - [kubectl](#kubectl)
      - [kubernetes Core Known Issues](#kubernetes-core-known-issues)
      - [Docker runtime Known Issues](#docker-runtime-known-issues)
      - [Rkt runtime Known Issues](#rkt-runtime-known-issues)

--- a/docs/proposals/rescheduling.md
+++ b/docs/proposals/rescheduling.md