CoreDNS should respect user taints

Otherwise users will be surprised when CoreDNS starts running on their
masters, where kube-dns did not.

Issue #70851
This commit is contained in:
Justin SB 2018-11-09 09:25:35 -05:00
parent 1f56cd801e
commit 0d57176f40
No known key found for this signature in database
GPG Key ID: 8DEC5C8217494E37
3 changed files with 0 additions and 6 deletions

View File

@ -108,8 +108,6 @@ spec:
spec:
serviceAccountName: coredns
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
- key: "CriticalAddonsOnly"
operator: "Exists"
containers:

View File

@ -108,8 +108,6 @@ spec:
spec:
serviceAccountName: coredns
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
- key: "CriticalAddonsOnly"
operator: "Exists"
containers:

View File

@ -108,8 +108,6 @@ spec:
spec:
serviceAccountName: coredns
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
- key: "CriticalAddonsOnly"
operator: "Exists"
containers: