<p>I'm currently using Kubernetes for our staging environment - and because it is only a small one, I'm only using one node for <code>master</code> and for running my application pods on there.</p>

<p>When we switch over to production, there will be more than one node - at least one for master and one bigger node for the application pods. Do I have to make sure that all my pods are running on a different node than <code>master</code> or does Kubernetes take care of that automagically?</p>

<p>If you look at the output of <code>kubectl get nodes</code>, you'll see something like:</p>

<pre><code>~ kubectl get nodes
NAME                                     STATUS                     AGE       VERSION
test-master              Ready,SchedulingDisabled   23h       v1.6.0-alpha.0.1862+59cfdfb8dba60e
test-minion-group-f635   Ready                      23h       v1.6.0-alpha.0.1862+59cfdfb8dba60e
test-minion-group-fzu7   Ready                      23h       v1.6.0-alpha.0.1862+59cfdfb8dba60e
test-minion-group-vc1p   Ready                      23h       v1.6.0-alpha.0.1862+59cfdfb8dba60e
</code></pre>

<p>The <code>SchedulingDisabled</code> tag ensures that we do not schedule any pods onto that node, and each of your HA master nodes should have that by default. </p>

<p>It is possible to set other nodes to <code>SchedulingDisabled</code> as well by using <a href="http://kubernetes.io/docs/user-guide/kubectl/kubectl_cordon/" rel="nofollow noreferrer">kubectl cordon</a>.</p>
