Welcome to the Linux Foundation Forum!

Coredns deployment question

Posts: 37
edited May 2021 in LFS258 Class Forum

Could coredns deployment not being replicated to the master be an issue. When checking on the which nodes were running the coredns, I noticed it was only on worker nodes and not the master. Please see below.

And from looking at the details of the pods I can see that the 'selector' has chosen these nodes due to a value of:
kubernetes.io/os=linux

Furthermore I see the following under 'tolerations'...and it would appear this might be 'why' the master isn't running a 'coredns' pod...am I reading this correctly?

  1. tolerations:
  2. - key: CriticalAddonsOnly
  3. operator: Exists
  4. - effect: NoSchedule
  5. key: node-role.kubernetes.io/master
  6. - effect: NoSchedule
  7. key: node-role.kubernetes.io/control-plane
  8. - effect: NoExecute
  9. key: node.kubernetes.io/not-ready
  10. operator: Exists
  11. tolerationSeconds: 300
  12. - effect: NoExecute
  13. key: node.kubernetes.io/unreachable
  14. operator: Exists
  15. tolerationSeconds: 300

Just wondering what the best practice should be. Thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training