kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

addressed reviewer comments

This commit is contained in:
Bobby (Babak) Salamat 2018-01-17 00:12:57 -08:00
parent a57cd1042f
commit b887569721
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/scheduling/pod-preemption.md
View File

@ -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 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 the "scheduler.kubernetes.io/nominated-node-name" key to the pod. This key is referred to as
"NominatedNodeName" in this doc for brevity. "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 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 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 list and add them to the scheduling queue. (Scheduler should keep its existing rate