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

Merge pull request #20868 from jqmichael/patch-3

Browse Source 
Clarify node affinity in ScheduleDaemonSetPods
This commit is contained in:
Kubernetes Prow Robot
2020-05-21 10:20:14 -07:00
committed by GitHub
parent d627127cbe 691f8667c6
commit 782ff1b757
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/daemonset.md
+1 -1
View File
@@ -125,7 +125,7 @@ That introduces the following issues:
scheduler instead of the DaemonSet controller, by adding the `NodeAffinity` term scheduler instead of the DaemonSet controller, by adding the `NodeAffinity` term
to the DaemonSet pods, instead of the `.spec.nodeName` term. The default to the DaemonSet pods, instead of the `.spec.nodeName` term. The default
scheduler is then used to bind the pod to the target host. If node affinity of scheduler is then used to bind the pod to the target host. If node affinity of
the DaemonSet pod already exists, it is replaced. The DaemonSet controller only the DaemonSet pod already exists, it is replaced (the original node affinity was taken into account before selecting the target host). The DaemonSet controller only
performs these operations when creating or modifying DaemonSet pods, and no performs these operations when creating or modifying DaemonSet pods, and no
changes are made to the `spec.template` of the DaemonSet. changes are made to the `spec.template` of the DaemonSet.