Yuvi

> I guess it seems simple now that I write it all out. But I had to dig deep into a lot of nested configuration, find undocumented scripts, read the...

@tjcrone > Maybe the core of the core of the problem is that we are using repo2docker which doesn't really do what we need it to do, and then another...

@scottyhq > One advantage I also anticipate for sticking to just Dockerfiles is faster build times though the use of `docker build --cache-from `. I've noticed that `onbuild` images using...

Yeah, might be useful to output a kubeconfig file locally, and then set the `KUBECONFIG` env var to point to it? Terraform definitely doesn't wanna change your ~/.kube/config...

`hubploy` doesn't depend on `KUBECONFIG` - it gets credentials from the keys set in `hubploy.yaml`. Current environment variables shouldn't matter, and I'd prefer to not have hubploy modify anything in...

I just worked with @super-cob a little on this. Based on my understanding of how backends work, the use case is *slightly* different - we want to have two different...

We could also use https://www.terraform.io/docs/providers/random/r/pet.html or https://www.terraform.io/docs/providers/random/r/id.html, but for our usage I prefer prefixing instead.

See https://medium.com/@pavloosadchyi/terraform-patterns-and-tricks-i-use-every-day-117861531173 talking about prefixes. I think this matches our use case very well

Managed nodegroups also *just* got the ability to be in private subnets.

There's also problems with scoping. For example, the cluster autoscaler role only needs access to resources created by a specific EKS cluster. This keeps roles as tightly scoped as possible....