<p>The autoscaler plugin works great, but it defaults to a 10 minute cooldown for unneeded nodes. Since AWS has per-second billing, we'd like to scale down faster to reduce cost.</p>
<p>Is the cooldown period configurable in the kops InstanceGroup or the cluster autoscaler?</p>

YVG
<p>You need to apply <code>--scale-down-unneeded-time</code> flag while defining autoscaler in deployment configuration file:</p>
<p>Here is an example:</p>
<pre><code> command:
   - ./cluster-autoscaler
   - --cloud-provider=aws
   - ...
   - --scan-interval=25s
   - --scale-down-unneeded-time=30s
</code></pre>
<p>It is useful to add also <code>--scan-interval</code> flag.</p>
<p><strong>Also remember that short cooldowns can cause Over-Scaling / Under-Scaling.</strong></p>
<p>Cooldown durations should instead be <em>at least</em> the amount of time it takes the target metric to reach its new “normal” after a scaling event. If it takes three minutes for your CPU utilization to drop by about 50% after scaling up 2x, a cooldown less than three minutes causes AWS to scale out again before the previous scale out has had time to take effect on your metrics, causing it to scale out more than necessary.</p>
<p>Take a look: <a href="https://segment.com/blog/when-aws-autoscale-doesn-t/" rel="nofollow noreferrer">autoscaling-aws</a>, <a href="https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#i-have-a-couple-of-nodes-with-low-utilization-but-they-are-not-scaled-down-why" rel="nofollow noreferrer">kubernetes-autoscaler</a>, <a href="https://d1.awsstatic.com/events/reinvent/2019/REPEAT_3_Deep_dive_Kubernetes_auto_scaling_CON418-R3.pdf" rel="nofollow noreferrer">autoscaler-aws-kubernetes</a>.</p>
