TL;DR: No. And you might actually come out ahead.
The Kubernetes community dropped some heavy news in late 2025: the widely-used Ingress NGINX controller is being retired in March 2026. For years, it's been maintained by a small group of dedicated volunteers working nights and weekends. Despite community-wide calls for help, no new maintainers stepped up. The project is done.
If you're running NGINX Ingress in production, this might feel like a crisis. At K-Ops, we see it as an opportunity for Pragmatic Engineering: a forced migration that pushes you toward more efficient, modern standards.
Note: While we use Istio as our example, these principles are platform-agnostic. Whether you are running on GKE, EKS, AKS, or bare metal—if it's Kubernetes, the move to Gateway API is a universal win.
Why This Might Actually Be Good For You
The forced migration is pushing the ecosystem toward Strategic Frugality: modern solutions that actually simplify your infrastructure and reduce management overhead. Here is what we discovered while migrating workloads to Istio using the Gateway API:
- One gateway, multiple protocols: With NGINX Ingress, routing TCP traffic (like Jenkins JNLP agents or Gitea SSH) often meant awkward workarounds: LoadBalancer services, ConfigMap hacks, or running extra SSL termination sidecars. With Gateway API's
HTTPRouteandTCPRoute, it all flows through the same infrastructure. TLS terminates once at the edge, and everything stays efficient. - Less infrastructure overhead: No more messy LoadBalancer services eating cloud costs for every individual service. No sidecar containers bloating your pods. Centralized TLS management. Cleaner, simpler, and significantly cheaper.
- Better performance: Modern implementations like Istio (built on Envoy) are simply faster than the aging NGINX Ingress. You get lower latency, efficient hot-reloading, and better resource usage.
What About Alternatives?
We evaluated several options with our "whatever works" mindset. We tried Traefik first, but found the Gateway API support felt half-baked for high-traffic needs and the performance didn't hit our benchmarks.
Istio worked out of the box and is a CNCF graduated project. Other solid options for your stack include:
- Apache APISIX: Built on OpenResty/NGINX but with a modern, API-first control plane. It's a great choice if you want NGINX's familiarity with modern capabilities.
- Kong: Enterprise-friendly with a massive plugin ecosystem and a very mature Gateway API implementation.
- HAProxy: If raw performance and battle-tested reliability are your only metrics, HAProxy remains a king for high-traffic organizations.
- F5 NGINX Ingress Controller: If you must stay on NGINX, this version is separately maintained from the retiring community version and remains actively supported.
The Real Story: Sustainability
This isn't just about technical debt. It's about open source sustainability. Mission-critical infrastructure maintained by exhausted volunteers eventually breaks. The responsible thing is exactly what happened: a clear end-of-life date instead of letting it become a security nightmare.
Conclusion: Don't Panic, Migrate
The Gateway API is where the Kubernetes ecosystem is heading anyway. NGINX Ingress reaching its end-of-life just gave you the push you needed to modernize. You'll likely end up with a setup that is more performant, easier to manage, and cheaper to run.
Ready to migrate your ingress layer before the March 2026 deadline?
K-Ops is ready to help you architect your move to the Gateway API.