Evidence boundary: The March 2026 KubeCon appearance was retrospective evidence, not a new migration phase. The exact historical completion day is not public.
What was reported
Zapier replaced ingress-nginx with Envoy Gateway and moved production routing from Kubernetes Ingress resources to Gateway API HTTPRoutes.
Verified facts
- Approximately 500 production ingresses were migrated in less than six months.
- Envoy Gateway now powers Zapier's inbound and cross-service traffic.
- Staging migration and a bake-in period preceded production cutover.
- The broader planning and execution effort took close to a year.
- The platform processes about 200 million production requests per hour.
Migration method
Zapier used an incremental approach, including weighted DNS, staged validation and explicit handling of behavioural differences between the old and new ingress defaults.
What is not established
- The exact calendar day of final production completion.
- A published count of clusters or applications affected.
- An explicit statement that every development-cluster ingress-nginx instance was decommissioned, although the production scope is clearly complete.
PlatformTrace analysis
This is a well-evidenced production replacement, but it belongs in the corpus as a historical backfill. The March 2026 conference talk confirms the engineering story without creating a new migration event.
Sources
Corrections and updates
No correction is currently open. New routing-platform phases or materially revised scale figures will be recorded as dated updates.