Replacing NGINX with Envoy in a Traffic Control System
summary
Migrates a product proxy from NGINX to Envoy over about six months by replacing the custom nginx binary with Envoy, building an XDS management service and an access log gRPC pipeline, backporting features (mac build, subset load balancing, endpoint metadata) to Envoy, and validating with a canary for a week before full rollout. Claims: dynamic gRPC config and streamed logs remove sidecars and file reloads, latency and footprint remain acceptable, and the management pieces are being open sourced and work in production.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:03They're the sole scalable fix to tech debt
- 2:47Turbine Labs
- 3:47Thoughts on the early plan
- 9:31Envoy benefits
- 11:25We need more than a feature list
- 13:25Fast, light and predictable
- 14:47Planning the migration: Feature Parity
- 19:59Phase I work items
- 24:03Lesson learned
- 25:51Not rocket science
- 27:35Open sourcing envoy simple
related talks
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
15mFrom ingress-nginx to Envoy Gateway at Zapier: The...
26mRedesigning Ingress: Docker’s Transition To the Next-Gen Gateway API
28mDeploying hybrid topologies with k8s & Envoy: a look at service discovery
06mOpening Remarks
17mLessons Learned: Four Years with Emissary-ingress and Envoy
35mBack To the Basics - Service Mesh Fundamentals
33mEnvoy Gateway Project Update