About this episode

William Morgan discusses the challenges service meshes address for platform teams using Kubernetes.

Network calls fail in ways function calls never do - and once a monolith becomes microservices, reliability problems show up fast: retries amplify load, latency spikes cascade, and “what talks to what?” becomes hard to answer. William Morgan, co-creator of Linkerd and the person who coined “service mesh,” breaks down what service meshes actually solve for platform teams running Kubernetes at scale. The conversation focuses on practical outcomes: improving reliability between services, getting uniform observability without rewriting every app, and handling gaps Kubernetes doesn’t cover well - like gRPC/HTTP2 load balancing and cross-environment communication. Key topics Why reliability is the first “microservices tax” (timeouts, retries, backoff, cascading failure) What Kubernetes does not solve at the networking layer—and where a service mesh fits gRPC/HTTP2 load balancing problems and why L4 balancing can fall short Service-to-service visibility: understanding traffic flows and performance without per-app instrumentation Cost and resilience tradeoffs with multi-AZ Kubernetes on AWS (and how zonal-aware balancing can help) Whether developers should ever need to interact with…

People in this episode

Host: Cory O'Daniel

Guest: William Morgan

Topics covered

• service meshes
• Kubernetes
• microservices
• reliability
• observability
• traffic management

Keywords

• service mesh
• microservices tax
• gRPC
• HTTP2
• load balancing
• observability
• Kubernetes networking

Mentioned in this episode

Organizations: Buoyant, Linkerd, Kubernetes, AWS

More episodes of Platform Engineering Podcast

• Taking a Summer Break: What Would You Like To Hear This Fall? · July 15, 2026 · 3 min

Explore listener stats, chart rankings, contacts and more on the Platform Engineering Podcast podcast page.