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

Merge pull request #2383 from Huang-Wei/revise-schedule-DS-pod-by-scheduler 

fix a mis-placed section in schedule-DS-pod-by-scheduler.md
This commit is contained in:
k8s-ci-robot 2018-07-22 23:41:17 -07:00 committed by GitHub
parent 1ee42511e6 2defcec274
commit 1171a23ab2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
contributors/design-proposals/scheduling/schedule-DS-pod-by-scheduler.md
View File

@ -45,11 +45,6 @@ This option is to leverage NodeAffinity feature to avoid introducing scheduler
1. DS controller filter nodes by nodeSelector, but does NOT check against scheduler’s predicates (e.g. PodFitHostResources)
2. For each node, DS controller creates a Pod for it with the following NodeAffinity
3. When sync Pods, DS controller will map nodes and pods by this NodeAffinity to check whether Pods are started for nodes
4. In scheduler, DaemonSet Pods will stay pending if scheduling predicates fail. To avoid this, an appropriate priority must
be set to all critical DaemonSet Pods. Scheduler will preempt other pods to ensure critical pods were scheduled even when
the cluster is under resource pressure.
```yaml
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
@ -60,6 +55,10 @@ nodeAffinity:
values:
- dest_hostname
```
3. When sync Pods, DS controller will map nodes and pods by this NodeAffinity to check whether Pods are started for nodes
4. In scheduler, DaemonSet Pods will stay pending if scheduling predicates fail. To avoid this, an appropriate priority must
be set to all critical DaemonSet Pods. Scheduler will preempt other pods to ensure critical pods were scheduled even when
the cluster is under resource pressure.
## Reference