diff options
| author | Bobby (Babak) Salamat <bsalamat@google.com> | 2018-01-17 00:12:57 -0800 |
|---|---|---|
| committer | Bobby (Babak) Salamat <bsalamat@google.com> | 2018-01-17 00:12:57 -0800 |
| commit | b8875697214eb3a3eb3f1c5356afe5e92d51c591 (patch) | |
| tree | 11b3f283ff4e9aebf876350e3efd6e3ccf3d24bf | |
| parent | a57cd1042f92ee48beb39b6443bfa72e7e09c300 (diff) | |
addressed reviewer comments
| -rw-r--r-- | contributors/design-proposals/scheduling/pod-preemption.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/contributors/design-proposals/scheduling/pod-preemption.md b/contributors/design-proposals/scheduling/pod-preemption.md index 106b1f9b..c83f83d2 100644 --- a/contributors/design-proposals/scheduling/pod-preemption.md +++ b/contributors/design-proposals/scheduling/pod-preemption.md @@ -151,6 +151,8 @@ The head of the queue will always be the highest priority pending pod. 1. If a node was chosen to preempt pods, set the node name as an annotation with the "scheduler.kubernetes.io/nominated-node-name" key to the pod. This key is referred to as "NominatedNodeName" in this doc for brevity. + When this annotation exists, scheduler knows that the pod is destined to run on the + given node and takes it into account when making scheduling decisions for other pods. 1. When any pod is terminated, a node is added/removed, or when pods or nodes updated, remove all the pods from the unschedulable pods list and add them to the scheduling queue. (Scheduler should keep its existing rate |