Application Networking on Kubernetes, where are we now?
summary
Claims that Envoy sidecars plus Istio provide observability, retries, mTLS and fine routing but require control-plane components and many per-pod proxies. Demonstrates EKS, Kubernetes Gateway API controller and Amazon VPC Lattice as concrete tools: the controller auto-creates service networks and exports/imports services, and Lattice routes across VPCs and accounts to EC2, EKS and Lambda without deploying sidecars. Presents this as a working alternative that removes sidecar maintenance while keeping layer‑7 routing, security and observability.
AI-written summary · about
chapters (16)
- 0:00Kubernetes networking intro
- 1:00Monoliths to microservices
- 3:33Distributed systems challenges
- 5:02EKS and VPC networking
- 6:46Networking patterns evolution
- 7:28Service mesh and sidecars
- 10:23Control plane vs data plane
- 11:07Service mesh use cases
- 13:18Envoy as proxy
- 14:20Istio deployment
- 15:50Service mesh limits
- 16:33Gateway API evolution
- 18:41VPC Lattice overview
- 20:05VPC Lattice components
- 21:31Gateway API with Lattice
- 24:17Summary
related talks
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
15mSimplify Kubernetes Connectivity
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
50mService Mesh and Sidecars with Istio and Envoy
25mIstio and why do we need it
28mApplication delivery on k8s - the past, present and future
52mMaking microservices micro with Istio Service Mesh & Kubernetes
32mService Networking Within Air-Gapped Environments: Deployment Strategies and Operat...
