<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>There is no such capability to create nodes with a new specification, and I don't think it is necessary as well. Imagine a typo in nodeLabel bringing up new nodes, and also these new nodes are not known to your IAC is another scary thing. Cluster autoscaler adds new nodes by updating your autoscaling group, so node is same as other nodes in that autoscaling group.
if you want to hack around you can check <a href="https://kubernetes.io/docs/reference/access-authn-authz/" rel="nofollow noreferrer">admission-controllers</a>, add existing nodes with this new label or modify label on the fly to one you support? But do you really need to do it?</p>
