Information Security Engineer at a outsourcing company with 1,001-5,000 employees
Reseller
Top 20
Mar 12, 2026
In my opinion, NGINX Ingress Controller can make better improvements for ingress control, and I think they are already the leader in the Ingress and Gateway API. The Gateway API has the capability to separate the gateway responsible for the FQDN and certificate management. They separate this part within the gateway, and another part is the HTTP route which will load balance to the backend service. F5 has this kind of deployment for many years before the announcement of the Gateway API itself. Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller.
Python Developer and Application Analysts at All Solutions
Real User
Top 20
Jan 4, 2026
One improvement I see for NGINX Ingress Controller is that the obvious downside is the cost, as you pay for the license on top of AWS infrastructure and the pricing is not cheap. However, compared with the cost of development time, downtime, or buying multiple tools, it is often justified, so cost awareness is still necessary. I would like to see a more visual management UX and even stronger AWS native integration patterns.
Container Management is essential for efficiently deploying and maintaining applications in microservices architectures, enhancing scalability and reliability.This practice involves orchestrating containerized applications to optimize resources and streamline application lifecycle management. Users gain improved control over infrastructure, enabling faster deployment cycles and simplification of complex cloud-native operations. Popular solutions offer automated updates, clustering, and...
In my opinion, NGINX Ingress Controller can make better improvements for ingress control, and I think they are already the leader in the Ingress and Gateway API. The Gateway API has the capability to separate the gateway responsible for the FQDN and certificate management. They separate this part within the gateway, and another part is the HTTP route which will load balance to the backend service. F5 has this kind of deployment for many years before the announcement of the Gateway API itself. Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller.
One improvement I see for NGINX Ingress Controller is that the obvious downside is the cost, as you pay for the license on top of AWS infrastructure and the pricing is not cheap. However, compared with the cost of development time, downtime, or buying multiple tools, it is often justified, so cost awareness is still necessary. I would like to see a more visual management UX and even stronger AWS native integration patterns.