Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request kubernetes#52193 from StevenACoffman/kube-dns-anti…
…-affinity Automatic merge from submit-queue (batch tested with PRs 53106, 52193, 51250, 52449, 53861). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. kube-dns-anti-affinity: kube-dns never-co-located-in-the-same-node **What this PR does / why we need it**: This is upstreaming the kubernetes/kops#2705 pull request by @jamesbucher that was originally against [kops](github.com/kubernetes/kops). Please see kubernetes/kops#2705 for more details, including a lengthy discussion. Briefly, given the constraints of how the system works today: + if you need multiple DNS pods primarily for availability, then requiredDuringSchedulingIgnoredDuringExecution makes sense because putting more than one DNS pod on the same node isn't useful + if you need multiple DNS pods primarily for performance, then preferredDuringScheduling IgnoredDuringExecution makes sense because it will allow the DNS pods to schedule even if they can't be spread across nodes **Which issue this PR fixes** fixes kubernetes/kops#2693 **Release note**: ```release-note Improve resilience by annotating kube-dns addon with podAntiAffinity to prefer scheduling on different nodes. ```
- Loading branch information