Wylie Hobbs

Looks to be related to issue #89 in terraform-aws-eks

This actually is not related to protect_from_scale_in but how cluster-autoscaler is designed to work. Before, we could set maxSize to 0 and all instances in the ASG would be terminated....

@stefansedich [This issue](https://github.com/kubernetes/autoscaler/issues/1555) is tracking the root of the problem, which is that cluster-autoscaler does not respect max_size 0 (and in fact gets totally confused by it). I should rename...

I guess that's something you would have to set a good max_size to prevent - it's possible new nodes would get created in blue but not likely unless you have...

Removing protect_from_scale in is not recommended as it will allow both the ASG and CA to be able to perform autoscaling duties. Maybe it's not a big deal for you...

Setting max_size to 0 will make CA ignore it because it gets confused and is not expecting that value to be 0. The AWS ASG will respect it when you...

@antonbabenko This method does not work without modifications to the module to support multiple provider configurations. Your comment in #146 led me to believe you don't want to support multiple...

Thanks for the quick response! I'll see what I can figure out.