<p>If a single Kubernetes cluster is built and runs some number of pods, however the single node carries a <code>PreferNoSchedule</code> taint, it would would make sense to migrate these pods and workloads to more suitable, untainted nodes if they are added to the cluster.</p>
<p>Will this happen automatically in &gt;= 1.6 or will it need to be triggered? How is it triggered?</p>

Alex Turner
<p>In this scenario, there will be no action triggered towards the kube-scheduler to schedule pods even though a new worker is added to a cluster.</p>
<p>For the pods to be moved to a new worker, we need to trigger a new pod scheduling requirement.</p>
<p>Simple solution would be to scale down to 0 and scale up to the needed number of pods for each deployment.</p>
<pre><code>kubectl scale --replicas=&lt;expected_replica_num&gt; deployment &lt;deployment_name&gt;
</code></pre>
