super-cob
super-cob
Some orgs have security requirements to only have EC2 running in private subnets. Can we make this some kind of option for this terraform deployment?
I notice the same behavior every time, when I create a cluster I get this error ```Error: Kubernetes cluster unreachable: Get https://0B2C668907D2EDACF583F44FC68724C1.gr7.us-east-1.eks.amazonaws.com/version?timeout=32s: dial tcp 34.233.112.65:443: i/o timeout on autoscaler.tf line...
This is a fork from https://github.com/yuvipanda/terraform-deploy/tree/fix/no-users and the idea is that you can `terraform apply` from the `aws-creds` folder to create a group that may assume a role from which...
Some orgs might have requirements that IAM Write permissions are very strictly guarded, so it would be easiest for those orgs to have the IAM roles that terraform needs created...
In our account's AWS Console, this Terraform script stood up a bunch of EC2 which don't show a name. We review everything to make sure there aren't accidental nodes up...
when I attempt to run this after the `cluster-autoscaler` IAM role already exists, I get this error ``` Error: Kubernetes cluster unreachable on autoscaler.tf line 63, in resource "helm_release" "cluster-autoscaler":...