Update coredns tolerations
Follow up from https://gitlab.cern.ch/kubernetes/project/-/issues/530
Current tolerations allow coredns pods to be scheduled on cordoned nodes.
Before:
- effect: NoSchedule
operator: Exists
After
- key: "node-role.kubernetes.io/master"
operator: "Exists"
effect: "NoSchedule"
This way the coredns pods can be scheduled on master nodes, but cannot be scheduled on cordoned nodes (cordoning a node adds key: node.kubernetes.io/unschedulable
).