<p>Suppose we have 4 nodes eks cluster in ec2-autoscaling min with 4 nodes.
A kubernetes application stack deployed on the same with one pod- one node. Now traffic increases HPA triggered on eks level. 
Now total pods are 8 pods ,two pods - on one node. Also triggered auto-scaling. Now total nodes are  6 nodes. </p>

<p>Its observed all pods remain in current state. Post autscaling also.</p>

<p>Is there a direct and simpler way?
Some of already running pods should automatically launch on the additional nodes (detect it and reschedule itself on the recently added idle worker/nodes (i:e non-utilized - by using force eviction of pods)</p>

<p>Thanks in Advance.</p>

<p>One easy way is to delete all those pods by selector using below command and let the deployment recreate those pods in the cluster</p>

<p>kubectl delete po -l key=value</p>

<p>There could be other possibilities. would be glad to know from others</p>
