<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>Take a look at the <a href="https://github.com/kubernetes-sigs/descheduler" rel="nofollow noreferrer">Descheduler</a>. This project runs as a Kubernetes Job that aims at killing pods when it thinks the cluster is unbalanced.</p>

<p>The <a href="https://github.com/kubernetes-sigs/descheduler#lownodeutilization" rel="nofollow noreferrer"><code>LowNodeUtilization</code></a> strategy seems to fit your case:</p>

<blockquote>
  <p>This strategy finds nodes that are under utilized and evicts pods, if
  possible, from other nodes in the hope that recreation of evicted pods
  will be scheduled on these underutilized nodes.</p>
</blockquote>

<hr>

<p>Another option is to apply a little of chaos engineering manually, forcing a Rolling Update on your deployment, and hopefully, the scheduler will fix the balance problem when pods are recreated. </p>

<p>You can use the <code>kubectl rollout restart my-deployment</code>. It's way better than simply deleting the pods with <code>kubectl delete pod</code>, as the rollout will ensure availability during the "rebalancing" (although deleting the pods altogether increases your chances for a better rebalance).</p>
