Deploying Service Mesh in Production
summary
Concrete guidance for running a service mesh in production: use Istio with Envoy sidecars, separate Istio control plane vs data plane into distinct namespaces, run gateways separately for ingress and inter-cluster traffic, and manage certificates for mTLS via your PKI. Demos show kubectl installs, labeling namespaces for injection, a revisions-based canary upgrade (observed proxy 1.9.5 → 1.10.0), and configuring the proxy to start before the app to avoid startup failures. Focus on observability, gradual rollout, and automation around upgrades.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:40Do you have supporting infrastructure?
- 9:19Service mesh "lite" aka "waypoints"
- 10:08Start at the edge!
- 11:00Pick a specific use case, iterate
related talks
30mIntroduction to Service Mesh for DevOps
21mProduction-Ready gRPC: How Service Meshes Simplify Security, Routing, and Observability
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
28mService Mesh: Demystifying Istio
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
26mAn Introduction to Service Mesh in Action
52mEmpower Your Microservices with Istio Service Mesh
52mMaking microservices micro with Istio Service Mesh & Kubernetes
