Service Mesh War Stories - Lessons Learned the Hard Way
summary
Panel boils down to concrete lessons: service meshes solve specific problems but add maintenance costs, upgrades are hard and running years‑old Istio is risky, many users install and forget. Surprising stories include Istio on an F-16, Linkerd powering train switching and medical devices, and Linkerd’s choice of Linkerd without Envoy. Common fixes are OPA for policy, shared control planes for multi‑cluster, Gateway API (v1alpha2) adoption, and shifting upgrades from quarterly toward less frequent, more automated rollouts.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:35Introductions
- 2:12Why should you use a service mesh
- 5:17Costbenefit analysis
- 7:46Surprising use cases
- 11:02Challenges
- 12:48Multitenancy
- 17:32Biggest ongoing debate
- 21:10Service Mesh on Kubernetes
- 23:21Multiple Service Meshes
- 28:50Plumbing
- 33:43Data Plane
related talks
30mService Mesh Is Still Hard. The Things we all Did Wrong & Tales of Woe
34mService Mess to Service Mesh
35mNavigating the Service Mesh Ecosystem
37mPanel Discussion: Ask Us Anything: Microservices and Service Mesh
33mService Meshes: Istio, Linkerd - or No Mesh at All?
36mPanel: Ask Me Anything: Microservices and Service Mesh [B]
43mWTF Do We Need a Service Mesh?
26mChoosing a Service Mesh