CoreDNS should respect user taints

Otherwise users will be surprised when CoreDNS starts running on their masters, where kube-dns did not. Issue #70851
2018-11-09 09:25:35 -05:00
parent 1f56cd801e
commit 0d57176f40
3 changed files with 0 additions and 6 deletions
--- a/cluster/addons/dns/coredns/coredns.yaml.base
+++ b/cluster/addons/dns/coredns/coredns.yaml.base
@@ -108,8 +108,6 @@ spec:
    spec:
      serviceAccountName: coredns
      tolerations:
-        - key: node-role.kubernetes.io/master
-          effect: NoSchedule
        - key: "CriticalAddonsOnly"
          operator: "Exists"
      containers:
--- a/cluster/addons/dns/coredns/coredns.yaml.in
+++ b/cluster/addons/dns/coredns/coredns.yaml.in
@@ -108,8 +108,6 @@ spec:
    spec:
      serviceAccountName: coredns
      tolerations:
-        - key: node-role.kubernetes.io/master
-          effect: NoSchedule
        - key: "CriticalAddonsOnly"
          operator: "Exists"
      containers:
--- a/cluster/addons/dns/coredns/coredns.yaml.sed
+++ b/cluster/addons/dns/coredns/coredns.yaml.sed
@@ -108,8 +108,6 @@ spec:
    spec:
      serviceAccountName: coredns
      tolerations:
-        - key: node-role.kubernetes.io/master
-          effect: NoSchedule
        - key: "CriticalAddonsOnly"
          operator: "Exists"
      containers: