3 ms·
Devops person here: I already know all of these answers and would still choose Kubernetes over hand-rolling all of this again and again. "Just use Packer, some
by 15155 6y ago
Devops person here: I already know all of these answers and would still choose Kubernetes over hand-rolling all of this again and again.
"Just use Packer, some AMIs, some ASGs, some CF templates, some ELBs, some EC2 instances!"
No thanks: I'll Terraform an EKS cluster in 30 lines of HCL and deploy my applications with a Dockerfile and a handful of YAML files.
- hardwaresofton 6y ago> CF Templates Yeah, this is where it kicked in for me. Never mind the fact that all of that is AWS specific and absolutely doesn't help you if you ever move clouds. Great to know all the stuff below, but Kubernetes is a wonderful abstraction layer above that stuff, and it gets better every day. CF could have become Kubernetes -- it was supposed to be, but it just never got the mixture right (and of course is AWS exclusive).
- jen20 6y agoI find the ridiculous false dichotomy between Terraform for Kubernetes and Cloudformation for more basic infrastructure even more ironic given that I am still the eighth most prolific contributor to Terraform _over three years after leaving HashiCorp_.
- ex_amazon_sde 6y agoBoth options are questionable.