CoreDNS pods running at every node. (Nodeselector.)

[franitel]

Environment:

• *Kubernetes on premises with more than 50 servers.
  We are running using several environments separated by nodeselector.

The issue is that we have several environment and each environment is using different kind of machines, some for production
some for testing purpose, some for dev, staging,... and we have detected that we have some coredns pods running on test machines then we want to keep these important pods in production.

nodeSelector:
  node.kubernetes.io/environment: "production"

then I was checking the kubespray playbook the last version and I saw that it is hardcoded in the coredns-deployment.yml.j2 file:

https://github.com/kubernetes-sigs/kubespray/blob/master/roles/kubernetes-apps/ansible/templates/coredns-deployment.yml.j2

a Proposal in how to solve the issue is to do the same that we have in the dns_extra_tolerations

create a variable in
https://github.com/kubernetes-sigs/kubespray/blob/master/roles/kubernetes-apps/ansible/defaults/main.yml

to allow specify the NodeSelector to this coredns-deployment.

Tell me if you need more details and thanks for your great job!!

Francisco Rodriguez

[floryut]

@franitel Don't hesitate to create a PR 😄

[bac-w]

it works like this for me
Without NodeSelector
dns_extra_tolerations: [{effect: NoExecute, key: "node-role.kubernetes.io/node"}]

[efrikin]

@franitel It PR already fixed your problem

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[franitel]

I closed this issue because already was resolved in other issue.
#7613
BR,
Francisco Rodriguez