Kubernetes, EKS, GitOps & releases
Service mesh in depth
A service mesh moves networking concerns — encryption between services, retries, timeouts, traffic splitting, per-request metrics and access rules — out of application code and into a layer of proxies the platform team runs. It is powerful and also one of the most over-adopted technologies in Kubernetes, so interviewers want both: how it works (sidecars, ambient mode, mTLS identities, Envoy) and when you would not use one. This topic covers the architecture, the data-plane models, Istio traffic management and security, Linkerd and Cilium as alternatives, and how to operate and debug a mesh.
Stage 3 · Production platforms
Know these first
After this topic you can
- Explain how a service mesh works and compare sidecar and ambient modes
- Roll out mutual TLS and identity-based authorisation
- Run canaries, set retries and timeouts sensibly and debug mesh 503s
Lessons
-
1Why a service mesh
- The problems it solves
- Architecture: data plane and control plane
-
2Data-plane models
- Sidecars
- Istio ambient mode
- Comparing meshes
-
3Traffic management
- Istio routing resources
- Resilience features, used carefully
-
4Security
- Mutual TLS and workload identity
- Authorisation policies
-
5Operating a mesh
- Observability
- Debugging
- Upgrades and cost
- When not to use a mesh
-
6Interview questions and model answers
- "What is a service mesh and why would you use one?"
- "Sidecar vs ambient mode?"
- "How does mTLS work in Istio?"
- "We're getting 503s between two services in the mesh. How do you debug it?"
- "How would you do a canary release with a mesh?"
- "What are the risks of retries in a mesh?"
- "When would you not use a service mesh?"