Everyone talks about Kubernetes like it’s the silver bullet for all infrastructure problems. Here’s the truth: it’s a hammer, and not every problem is a nail.
That said, if you’re running microservices and you have the people to support it, Kubernetes can actually make your life simpler.
When K8s Makes Sense for Small Teams
Use Kubernetes if:
- You’re running 5+ microservices
- You have 2+ engineers who can own infrastructure
- You need multi-region deployment
- You’re tired of manual scaling
Don’t use Kubernetes if:
- You have a single monolith
- Ops is one person’s side project
- You don’t have enough services to justify complexity
Making K8s Work with Small Teams
Here are the practices that actually save time:
- Managed services: Use EKS, GKE, or AKS. Running your own control plane wastes time.
- Helm charts: Standardize deployments so you’re not inventing YAML every release.
- ArgoCD: GitOps means your infrastructure is defined in Git, not manual CLI commands.
- Limits and requests: Set these properly from day one. Debugging resource issues later is painful.
- Observability: Prometheus + Grafana are non-negotiable. You need to see what’s happening.
What You Can Skip (For Now)
Don’t implement these until they’re actually causing problems:
- Service mesh (Istio, Linkerd) – adds complexity without immediate benefit
- Custom operators – managed services solve this better
- Multi-cluster setups – run one cluster well before running two
- Knative or serverless on K8s – it’s immature and adds layers
Keep it simple. You’re running infrastructure, not building it.