Is it better to use NGINX Ingress Controller or the newer Gateway API for traffic routing?

All answers to this question.

The Gateway API is definitely the future of Kubernetes networking, as it provides a more role-oriented approach, separating the concerns of infrastructure providers, cluster admins, and developers. It supports advanced traffic splitting and cross-namespace routing natively, which Ingress struggles with. However, NGINX Ingress is battle-tested and has massive community support. If you need simple L7 routing, NGINX is fine. If you are building a complex multi-tenant platform, the Gateway API’s extensibility will save you from "annotation hell" in your YAML files.

   Answered 2025-09-07 by Susan Rodriguez

Does your cloud provider already have a managed implementation of the Gateway API? Using a provider-specific controller can simplify the integration significantly.

   Answered 2025-09-08 by Richard Lewis

• That’s a valid question, Richard. Currently, GKE and AWS have decent support, but it's still evolving. I’ve found that using the Gateway API with a managed controller allows us to use Cloud Load Balancer features without writing custom CRDs. It’s a bit of a learning curve compared to the standard Ingress resources, but the granular control over HTTPRoutes makes blue-green deployments much easier to manage.

     Commented 2025-09-09 by Thomas Wright

Stick with NGINX for now if your team isn't familiar with CRDs. The Gateway API is powerful but adds a layer of abstraction that might complicate troubleshooting.

   Answered 2025-09-10 by Margaret Walker

• I agree with Margaret. Unless you specifically need features like header-based routing across multiple namespaces, the standard Ingress is much faster to set up and document.

     Commented 2025-09-11 by Susan Rodriguez