Node DaemonSet in Kubernetes Deployment Should Not Run On Master

[davidz627]

Currently the Daemonset constantly attempts to create the pod on master and fails because of resource limits. We should stop scheduling on master so that it does not continually loop attempted creation.

This is high priority as we have seen the daemonset pod kick off the api server from the master putting the whole cluster in a bad state.

[msau42]

Looking at my master node,

Taints:             <none>
Unschedulable:      true

My master daemonset pod:

Tolerations:     node.kubernetes.io/disk-pressure:NoSchedule
                 node.kubernetes.io/memory-pressure:NoSchedule
                 node.kubernetes.io/not-ready:NoExecute
                 node.kubernetes.io/unreachable:NoExecute

@janetkuo, do you know how to prevent daemonset pods from being scheduled on the master?

[msau42]

(this is gce, not gke)

[davidz627]

From https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/:

The unschedulable field of a node is not respected by the DaemonSet controller.

Looks like taints are respected though, but my thought is tainting the master node could have unwanted side-effects

[msau42]

I don't know if there are any such addons that want to run on all nodes, including the master.

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

[msau42]

/remove-lifecycle stale /lifecycle frozen