<p>I am running a Kubernetes cluster in AWS EKS and I set up the autoscaler. I tested the autoscaler and it worked as when the number of pods in a node exceeded 110 then new nodes were automatically added to the cluster and the pending pods entered running state.</p>
<p>After that, I deleted the deployment. It's been about 10 minutes and I see that all new nodes created by the autoscaler are already there and in ready state!</p>
<p>How long does it take for Kubernetes to delete them automatically? Does it down-scale the cluster automatically at all?</p>

<p>Although scaling down is a slow process the default scan interval is <strong>10 seconds</strong> if you are using the autoscaler to scale the nodes in EKS.</p>
<p>You can check the status of autoscaler using <strong>configmap</strong> and its a decision.</p>
<p>There could be a possibility that on the new node you have some system pod running so due to that EKS is not able to scale those nodes down or PDB(PodDisruptionBudget) is set for deployments.</p>
<p>Pod has the annotation <code>&quot;cluster-autoscaler.kubernetes.io/safe-to-evict&quot;: &quot;false&quot;</code></p>
<p>Read more about EKS scaling : <a href="https://docs.aws.amazon.com/eks/latest/userguide/autoscaling.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/autoscaling.html</a></p>
