The hater’s guide to Kubernetes

1. Innovation tokens: Companies have limited capacity for innovation. These should be spent on core business problems, not on adopting cutting-edge tech stacks.


2. Known vs. unknown unknowns: Established technologies have more known issues, while new technologies often have many unknown problems.


3. Operational costs: Adding new technologies increases operati

• Terraform: I manage most of my cloud infrastructure with Terraform. I declare EKS clusters, S3 buckets, roles, and RDS instances in my Terraform manifests. The state is sync'ed to an encrypted S3 bucket. This avoids getting into trouble in case something happens to my development laptop.


• Docker: I build everything as Docker images. Even stateful com

Among the safest bets to choose from are in the Cloud Native Computing Foundation’s “Graduated Projects”. These are well-established tools like Kubernetes, which are likely to be around for the long run, and there are many related/supporting tools and resources built around them.

• ingress-nginx: Ingress controller for Kubernetes. It provisions NGINX services to load balance traffic to my pods. It also manages a Network Load Balancer (NLB) on AWS which controls ingress to the cluster nodes. It handles unhealthy nodes and traffic shaping for me. Rock-solid and has a huge community.


• cert-manager: It automatically issues and rene