Production-Ready gRPC: How Service Meshes Simplify Security, Routing, and Observability
summary
Shows a working setup on DigitalOcean Kubernetes using Istio mTLS handled by sidecars to offload encryption and certificate rotation, with Prometheus/Grafana scraping sidecar metrics for tracing and latency. Configured destinationRule and VirtualService subsets route traffic with 50/50 to 100% canary switch without pod restart, plus retries and fault injection policies that produce observable 503 patterns. Namespace-level PeerAuthentication enforces strict MTLS so non-injected clients fail, and demo artifacts and example configs are available for reproduction.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:22gRPC production readiness
- 3:38Service meshes for gRPC
- 9:41Demo setup and canary
- 13:35Traffic routing with virtual services
- 14:58Securing services with mTLS
- 16:41Observability with Prometheus
- 18:26Fault injection and retries
- 18:47Q&A
related talks
47mDeploying Service Mesh in Production
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
34mService Mess to Service Mesh
26mAn Introduction to Service Mesh in Action
30mIntroduction to Service Mesh for DevOps
53mDo you need a Service Mesh?
52mEmpower Your Microservices with Istio Service Mesh
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
