Envoy Overview and Maintainer Q&A
Talkat KubeCon + CloudNativeCon North America 2019 · on Thursday, 2019-11-21· at 16:25· Room 1AB - San Diego Convention Center, Upper Level·
summary
A fast C++14 network proxy that becomes an out‑of‑process universal data plane, built with L3/L4 and L7 filter stacks and pluggable extensions; supports HTTP/1/2, gRPC, TCP/UDP proxying, TLS termination, stats/logging/tracing, and IP‑transparency tricks used in production. Configuration ships via the XDS API (proto gRPC streaming, JSON REST fallback) and work is underway on delta/on‑demand XDS, QUIC/UDP, and mobile transport sockets. Deployed as Lyft’s edge and sidecar mesh and rolled out to ~2,000 services, it works but control‑plane scaling and many custom control planes remain operational pain points.
AI-written summary · about
chapters (15)
- 0:00Start
- 3:38Goal of Envoy
- 5:33Envoy Is a Network Proxy
- 8:16Service Discovery
- 8:33Active-Passive Health Checking
- 9:24Observability
- 10:20Level Block Diagram of Envoy
- 14:33History of Envoy
- 25:47Can You Proxy with the Same Source Ip That the Client Used
- 26:30Common Pitfalls
- 27:55Panic Routing
- 38:48How Would You Explain Service Mesh both the Control Plane and Data Plane in Plain English
- 40:07Service Mesh
- 43:17Why Does Envoy Not Have Working Groups
- 59:51Motivation at Lift
