Deep Dive: Envoy
summary
Explains how Envoy extensions are actually built and deployed: extensions require static-linked C++ extensions composed of a protobuf config + implementation, with Lua usable only for HTTP and WebAssembly and gRPC-based out-of-process options still experimental. Shows a gzip filter example (encode_data hook), a tap/admin socket capture controlled via admin endpoints, and mentions three recent L4 protocol filters including Kafka support. Notes operational reality: control planes and scale matter — Salesforce runs about 5,000 Envoys in production.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:03Agenda
- 2:30Deployment Model
- 2:56Design Goals
- 4:33Extensibility
- 7:43Screenshot
- 8:09New Extensions
- 9:40C Extension
- 10:58Example
- 11:24Config
- 13:37Conclusion
- 14:04Extension model








