P
Back to articles
Tutorial4 min read

How Stack Overflow replaced Ingress-NGINX with a custom solution

Stack Overflow's engineering team migrated from Ingress-NGINX to Istio using Gateway API after Ingress-NGINX was retired. They tested NGINX Gateway Fabric (latency spikes), Traefik (couldn't converge 5K routes within 5 minutes), and chose Istio (~42s convergence) for stability and performance. The migration required rethinking routing structures for the Gateway API model.

Source: Stack Overflow Blog
How Stack Overflow replaced Ingress-NGINX with a custom solution

How Stack Overflow Replaced Ingress-NGINX With a Custom Solution

Stack Overflow's engineering team has shared a detailed postmortem of their migration from Ingress-NGINX to a custom-built Gateway API solution, offering valuable lessons for anyone running Kubernetes at scale. The migration was driven by necessity: in November 2025, the Kubernetes blog announced that Ingress-NGINX was being retired, forcing teams relying on the popular ingress controller to find alternatives.

Senior Platform Engineer Michael Frank documented the journey, which involved evaluating three Gateway API implementations — NGINX Gateway Fabric, Traefik, and Istio — before selecting a winner.

The Evaluation Process

The team built a rigorous testing infrastructure using HTTPBin and a custom Go server. They ran Requests Per Second benchmarks targeting 10,000 RPS with four replicas on e2-standard-4 Google Cloud nodes, with the client running on Azure Standard_DC8as_cc_v5 instances. They also ran route creation benchmarks with 5,000 HTTPRoutes to test scalability.

The results were revealing. NGINX Gateway Fabric showed significant latency spikes during route updates when managing 1,000 routes. Traefik took over five minutes to converge 5,000 routes — the test actually timed out. Istio converged in approximately 42 seconds, with NGINX at roughly 57 seconds.

Why Istio Won

Istio won primarily on stability and performance. Its convergence time for large route configurations was the best among the candidates, and it maintained consistent performance under load. However, the team noted that Istio's filter configurations were significantly more complex syntactically than the NGINX or Traefik equivalents — a tradeoff they deemed acceptable for the performance gains.

Some Gateway API features, like header modification, only handled static values in the implementations tested, requiring implementation-specific extensions for dynamic use cases. Complex integrations such as ngx_http_auth_request_module were particular pain points during the migration.

Key Lessons

The migration to the Gateway API is not just a drop-in replacement — it requires rethinking how routing rules are structured. The team found that the Gateway API's role-based design (separating GatewayClass, Gateway, and HTTPRoute resources) provided better separation of concerns compared to the Ingress model, but required more upfront configuration planning.

For organizations considering a similar migration, the team recommends starting the evaluation process early, building representative benchmarks that match your actual traffic patterns, and accounting for the complexity gap between implementations when estimating migration effort.

Related Articles