· 6 min read
The short answer
Kubernetes is a powerful platform, but it is also a platform you have to operate: upgrades, networking, access control, monitoring and security patches. For many small teams a managed container service gives most of the benefit with much less to maintain.
Signs Kubernetes is probably worth it
- You run several services that need independent scaling and deployment
- You need strong isolation between teams, tenants or workloads
- You depend on ecosystem tools that assume Kubernetes (operators, service mesh, GitOps across many services)
- Someone on the team will own the platform, or you have budget for ongoing support
- You need to run the same platform across clouds or on-premises
Signs a simpler platform will serve you better
- One to three services with predictable traffic
- No one on the team has time to learn and maintain Kubernetes
- Your main problems are manual deployments and missing monitoring, not orchestration
- You want the lowest possible operational overhead this year
Practical alternatives
On AWS, ECS on Fargate runs containers without managing servers and integrates with load balancers, IAM and CloudWatch. On Azure, Container Apps provides a similar experience. For very small workloads, a well-managed Linux VM with Docker Compose, automated deployments and backups can be entirely reasonable.
Whichever you choose, the foundations are the same: infrastructure as code, a CI/CD pipeline, secrets kept out of code, and monitoring with alerts that someone acts on. Those foundations also make a later move to Kubernetes much easier.
If you do choose Kubernetes
- Use a managed control plane (EKS or AKS) rather than running your own
- Define the cluster and its add-ons in Terraform and Helm
- Set resource requests and limits for every workload
- Give people the minimum access they need through RBAC
- Deploy through Git (for example with Argo CD) rather than kubectl from laptops
- Plan for version upgrades several times a year