Life After Ingress NGINX: How to Unify Kubernetes Traffic in One Stack
The Ingress NGINX project has reached End-of-Life. No more bug fixes. No more security patches. If your cluster still depends on it, the clock isn't ticking anymore... It's stopped.
This session was standing room only at KubeCon EU, so we're sharing it for everyone who couldn't make it. In under an hour, you'll get a clear picture of the Kubernetes traffic landscape post-Ingress NGINX, and a practical roadmap for what comes next.
What's covered:
The EOL reality — what it actually means for your security posture and why "we'll deal with it later" is no longer an option
Benchmark data — HAProxy vs. NGINX, Envoy, and Traefik across requests per second, latency percentiles, and error rates (spoiler: 2x the throughput, significantly less CPU, zero routing errors)
Three migration paths — choose the one that fits where you are today:
Ingress Migration — a 1-to-1 swap using the HAProxy Kubernetes Ingress Controller
Gateway API — move directly to the new standard with HAProxy Unified Gateway
Universal Mesh — unify North/South, East/West, and multi-cluster routing into a single stack
Ingress Migration Assistant — a purpose-built tool that takes the friction out of moving off NGINX
At KubeCon, multiple people said (unprompted) some version of the same thing: "We need to migrate from Ingress NGINX, and obviously everyone is recommending HAProxy." Join us at this webinar to find out why.
Don't just replace your stack. Upgrade it.
Speakers
