From ingress-nginx to Envoy Gateway at Zapier: The...
Talkat EnvoyCon Europe 2026 · on Wednesday, 2026-03-25· at 12:45· Hall 1-5 | Tram Zone | Cloud Native Theater·
summary
Zapier migrates roughly 500 production ingresses serving 60,000 requests per second from ingress‑nginx to Envoy Gateway, using incremental cutovers with weighted DNS and per‑service baselines. Key operational fixes: increase Envoy's 1 MB request buffer to stop abandoned retries, set backend connection and circuit‑breaker policies to avoid serialized latency, and avoid noisy reconciles (100,000+ events) by stopping unnecessary TLS secret churn. Upgrading Envoy Gateway to 1.5.3 drops control‑plane memory from ~80% to <20%, and a custom gRPC service Wavefinder adds JWT validation and context enrichment.
AI-written summary · about
chapters (13)
- 0:00Migration journey intro
- 1:27Why Kubernetes API Gateway
- 2:32Why Envoy Gateway stood out
- 3:15Pre-migration housekeeping
- 4:17Incremental migration strategy
- 6:04Unexpected migration challenges
- 7:48Reconciliation issues
- 8:51Latency spikes after migration
- 9:55Path normalization differences
- 11:41Post-migration upgrades
- 12:21Building with Wavefinder
- 13:02Migration results and benefits
- 13:54Q&A
related talks
36mReplacing NGINX with Envoy in a Traffic Control System
26mRedesigning Ingress: Docker’s Transition To the Next-Gen Gateway API
31mBehind the Scenes of Building a Gateway API Dataplane...
28mMaking the Leap: What Gateway API Needs To Support Ingress-NGINX Users
06mGet To Where You're Going With Kgateway
33mEnvoy Gateway Project Update
28mEmissary-Ingress: Intro And Deep Dive
25mHow Niantic switched Pokémon GO to use Envoy