Reputation: 13806
I want to deploy a DaemonSet for monitoring purpose. So these Pods need to be deployed in all Nodes.
A DaemonSet ensures that all (or some) Nodes run a copy of a Pod.
I am using a DaemonSet so that all nodes get a copy.
spec:
containers:
- name: fluentd
image: aerocloud.io/containers/fluentd:0.0.1
volumeMounts:
- name: varlog
mountPath: /var/log
volumes:
- name: varlog
hostPath:
path: /var/log
When I'm creating this DaemonSet
in my Kubernetes cluster, I don't see Pod running in my master node.
Pod for this DaemonSet are running in all nodes except Master node.
What am I missing here? How can I enforce scheduler to schedule a Pod in Master node?
Upvotes: 12
Views: 11251
Reputation: 3981
Since Kubernetes 1.6, DaemonSets do not schedule on master nodes by default. In order to schedule it on master, you have to add a toleration into the Pod spec section:
tolerations:
- key: node-role.kubernetes.io/master
effect: NoSchedule
For more details, check out the example YAML files in Kubernetss DeamonSet docu. It is also mentioned in the chapter How Daemon Pods are Scheduled.
Upvotes: 33