<p>I am working with Kubernetes 1.4.3 and my nodes look like the following:</p>

<blockquote>
<pre><code>ip-10-0-0-105.eu-central-1.compute.internal   Ready                      1d
ip-10-0-0-50.eu-central-1.compute.internal    Ready,SchedulingDisabled   1d
ip-10-0-1-126.eu-central-1.compute.internal   Ready                      1d
</code></pre>
</blockquote>

<p>Even though the master node is set to <code>SchedulingDisabled</code>, <code>Daemonsets</code> are still being scheduled on it.</p>

<p>Firstly, why? this did not happen on prior to K8S 1.4, and if its a new, how do i cancel that option or maybe use pod affinity to exclude the master node from running daemonset pods.</p>

<p>Thanks.</p>

<p>This was answered in <a href="https://github.com/kubernetes/kubernetes/issues/29108#issuecomment-233432397" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/29108#issuecomment-233432397</a></p>

<p>Basically, this is working as intended. DaemonSet pods will get scheduled on unschedulable nodes. In the future (not v1.4), this behavior will be selectable at the pod level (e.g., see <a href="https://github.com/kubernetes/kubernetes/issues/29178" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/29178</a>). For now, you can choose not to register your master node to avoid this problem.</p>
