add master specific key to coredns toleration
Closes #46 (closed)
Current coredns toleration allows any NoSchedule
taint to be ignored, including cordoning broken nodes (cordoning adds key: node.kubernetes.io/unschedulable
). By adding the specific master key, we allow coredns to be scheduled on master (as per https://gitlab.cern.ch/kubernetes/automation/releases/cern-magnum/-/blob/master/values.yaml#L840) but still take into consideration cordoning.