Anton Osmond

Putting use cases aside (although I have many), autoscaling groups already support min, max & desired size being 0. A node group is ultimately just an autoscaling group (and therefore...

@yann-soubeyrand The cluster autoscaler is just one use case but this issue shouldn't relate specifically to the cluster autoscaler. The issue should be that you can't set a size of...

@yann-soubeyrand I got to this issue from [here](https://github.com/terraform-providers/terraform-provider-aws/issues/13984). It's nothing to do with the cluster autoscaler, I simply want to create a node group with an initial size of 0....

I have 2 additional use cases for the same feature, both on EKS. 1. If you want to utilise node taints & tolerations for all your nodes, any EKS managed...

If it helps I ran with log level set to `TRACE` and noticed this in the logs: ``` 2019/12/17 12:46:44 [WARN] Provider "kubernetes" produced an invalid plan for kubernetes_cluster_role_binding.developer_cluster, but...

What's really strange is the final constraint check - `

I have the same problem i.e. would love to see interpolations in the backend config. Now that we have "environments" in terraform, I was hoping to have a single config.tf...

Hey @stefanprodan Maybe it's unexpected then but it does actually work for generic YAML files too. In my testing, the entire YAML file I used in a case where it...

> @antonosmond I think there is an incidental case, perhaps we can say it happens to recognise resources that have an object at root, perhaps `apiVersion` and `kind` are inferred...

I hit this issue today so I'd also like to see support for "multi terramate projects inside a single repository" which was what I was trying to do. Thanks!