<p><a href="https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler" rel="nofollow noreferrer">https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler</a></p>
<p>Use case - installing a deployment with nodeSelector. No existing node label matches. Autoscaler won't scale up. Anyone aware if autoscaler is capable of labeling fresh EC2 if there is demand for one?</p>
<p>We are deploying big umbrealla charts (60 pods+) that are replicas of real production environments. Some of the pods are crucial for whole chart to work. If it gets spreaded among a few nodes, and one of the node is having health problems more than one environment is affected. Having it fully deployed on one node reduces number of affected charts to one.</p>
<p>thanks</p>

Łukasz
<p>have you tried using a separate node group for the pods that are important to you and use taints and tolerations so only those pods get scheduled on those nodes. the autoscaler will make sure you have enough nodes in that node group to run your pods</p>
