A Developer’s Introduction to Service Mesh
summary
Builds a working mesh with HashiCorp Consul + Envoy on Kubernetes and shows concrete configs: a 50/50 traffic split routed by proxy, mTLS issued to each sidecar, and intent-based API allow rules enforced by proxy filters. Demonstrates certificate injection working between proxies, explains that tracing only works when apps add OpenTelemetry and that proxy traces are exported to Jaeger and metrics merged for Prometheus, and shows load‑balancing across Java and .NET instances.
AI-written summary · about
chapters (12)
- 0:00Service mesh intro for devs
- 1:28Why devs need service mesh
- 3:34Service communication core
- 5:01Proxies enable mesh
- 7:27Deploying proxies in K8s/VMs
- 8:30Service discovery
- 10:59Load balancing
- 13:48mTLS and API auth security
- 18:47Traffic management
- 21:52Telemetry in mesh
- 27:12Merging app and proxy metrics
- 28:59Summary
related talks
30mIntroduction to Service Mesh for DevOps
53mDo you need a Service Mesh?
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
34mService Mess to Service Mesh
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
39mDo you need a Service Mesh?
28mService Mesh: Demystifying Istio
19mService Mesh and Your Legacy Apps: Connecting to Kubernetes with Consul
