<p>I've a CA (Cluster Autoscaler) deployed on EKS followed <a href="https://eksworkshop.com/scaling/deploy_ca/" rel="nofollow noreferrer">this post</a>. What I'm wondering is CA automatically scales down the cluster whenever at least <strong>a single pod</strong> is deployed on that node i.e. if there are 3 nodes with the capacity of 8 pods, if 9th pod comes up, CA would provision 4th nodes to run that 9th pod. What I see is CA is continuously terminating &amp; creating a node randomly chosen from within the cluster disturbing other pods &amp; nodes.</p>

<p>How can I tell EKS (without defining minimal nodes or disabling scale-in policy in ASG) to <strong>not to kill the node having at least 1 pod running on it</strong>. Any suggestion would be appreciated.</p>

<p>You cannot use pod as unit. CA work with resources cpu and memory unit.</p>

<p>If the cluster does not have enough cpu or memory it add one new.</p>

<p>You have to play with your requests resources (in the pod definition) or redefine your node to take an instance type with more or less resources depending how many pod you want on each.</p>

<p>Or you can play with the param <code>scale-down-utilization-threshold</code></p>

<p><a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca" rel="nofollow noreferrer">https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca</a></p>
