Kubernetes microservices reference
A production-shaped Kubernetes stack: gateway + BFF at the edge, mesh sidecars between services, HPA autoscaling, service discovery with outlier ejection, and a GitOps loop as the only write path.
What this design does
The reference most teams converge on after two years of Kubernetes: traffic enters through a gateway and a BFF, services talk through mesh sidecars that handle mTLS, retries and outlier ejection, and nothing changes in the cluster except through git. Import it and replace the placeholder services with yours — the operational patterns stay exactly where they are.
The patterns it composes
- Gateway + Backend-for-frontend — one edge for TLS/auth, one aggregator shaped for the client
- Sidecar service mesh — mTLS, retries and timeouts live in the proxy, not in every codebase
- Service registry + discovery — services find each other by name; failing endpoints get ejected
- Elastic scale (HPA) — replicas follow live metrics, not capacity guesses
- Health checks + outlier ejection — bad pods leave the load-balancing pool automatically
- GitOps declarative reconciliation — git is the desired state; a controller makes reality match
Import it, attach your own numbers, and verify the design against failures — or read the engineering notes.