The local Kubernetes series is complete — 16 parts.
If you're new and just arrived — start with chapter one on the inner dev loop. This final one pulls it all together: what we built and where to grow next.
What we ended up with — a real (not emulated) cluster on your laptop: k3d + a FastAPI image + real manifests (Deployment/Service/Ingress) + a fast inner loop on Tilt + PostgreSQL alongside + config/secrets + probes and limits + k9s. The main payoff is environment parity: manifest, RBAC, and service discovery problems show up locally, not via alerts at 3 a.m.
And three honest directions to grow (don't grab all at once):
• GitOps (Argo CD / Flux) — when the team and the number of environments grow;
• an observability stack (kube-prometheus-stack, Prometheus Operator, OpenTelemetry) — with a warning: a heavy stack can take down a weak k3d;
• remote development (Telepresence, mirrord) — and the difference between mirror mode (a copy of traffic, safe) vs steal (interception).
Read the finale and jump back to any chapter: https://dorokhovich.com/blog/local-k8s-conclusion-and-next-steps?utm_source=devto&utm_medium=syndication&utm_campaign=local-k8s-conclusion-and-next-steps
Top comments (0)