whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merged master into release-1.10 and resolved merge conflicts.

Browse Source
This commit is contained in:
Andrew Chen
2018-03-13 16:36:07 -07:00
parent 1500d69283 b34babb518
commit 021502d2a6
18 changed files with 183 additions and 258 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/configuration/pod-priority-preemption.md
+5 -4
View File
@@ -220,10 +220,11 @@ can be scheduled on N. P might become feasible on N only if a Pod on another
Node is preempted. Here's an example:
* Pod P is being considered for Node N.
* Pod Q is running on another Node in the same zone as Node N.
* Pod P has anti-affinity with Pod Q.
* There are no other cases of anti-affinity between Pod P and other Pods in the zone.
* In order to schedule Pod P on Node N, Pod Q should be preempted, but scheduler
* Pod Q is running on another Node in the same Zone as Node N.
* Pod P has Zone-wide anti-affinity with Pod Q
(`topologyKey: failure-domain.beta.kubernetes.io/zone`).
* There are no other cases of anti-affinity between Pod P and other Pods in the Zone.
* In order to schedule Pod P on Node N, Pod Q can be preempted, but scheduler
does not perform cross-node preemption. So, Pod P will be deemed unschedulable
on Node N.