NGINX Ingress Controller's governance and security features of AI capabilities are good, with all the basic guardrails available. The accuracy and reliability of NGINX Ingress Controller's AI capabilities are not 100%. Sometimes it hallucinates and requires more prompting to get what I want exactly, but overall it is a good feature that still needs improvements. NGINX Ingress Controller is a good tool to use. If you have a Kubernetes cluster, then it is easy to deploy and use, though you might face issues with the annotation part. I would give this review a rating of 9.
Technical Lead: Cloud Engineering at Fiftytwo Digital Limited
Real User
Top 10
May 24, 2026
My advice to others looking into using NGINX Ingress Controller is to review the documentation first and ensure it serves your purpose. On a scale of one to ten, I rate NGINX Ingress Controller overall as a nine. I chose nine because I do not know the complete use case of the product, so I do not give it a perfect ten. That is my opinion, and while I have encountered some problems and hurdles, I have overcome all of them. It has worked very well for my purposes.
Senior Network At Dxc Technology Professional at DXC Technology
Real User
Top 5
May 7, 2026
NGINX Ingress Controller is functional, but it is achievable and may take some extra time. The major issues typically relate to vulnerabilities, which F5 addresses with patches that require timely software upgrades to mitigate. I would rate this review a nine overall.
NGINX Ingress Controller as a reverse proxy itself, which I have already tested as a software as a standalone server and not just as an Ingress Controller, is perfect. As an Ingress Controller, it is doing fine. NGINX Ingress Controller must perform reverse proxy functions, path-based routing or host-based routing, and target which container to route traffic. It is deep technical work, but it is doing fine overall. Configuration is simple to start. To get deeper, I need to be a developer. Prometheus and Grafana are definitely necessary. The metrics I find really important is latency and request latency. That is one of the major metrics we love. I have configured a new use case once in my life when something required it to work. I did not test it again after that, just once in my life. Deployment works at small, medium, and large scales. I am working with different deployments. For the sales and pre-sales, I simplify the message as much as possible. The message for NGINX Ingress Controller is always complicated when delivered, and it requires simplification. I would rate this product 9 out of 10.
While I have not compared NGINX Ingress Controller with other solutions, I find all of its features, such as load balancing, security, and exposing multiple services behind one IP, to be the best facilities NGINX Ingress Controller is providing. We check all those aspects whenever we encounter any issues in production related to NGINX Ingress Controller. My advice for others looking into using NGINX Ingress Controller is that if you are using Google Cloud Platform, then you should definitely go with it as it is good.
Information Security Engineer at a outsourcing company with 1,001-5,000 employees
Reseller
Top 20
Mar 12, 2026
I would like to see some AI capabilities, in-built AI capabilities in NGINX Ingress Controller to help with the load balancing. Normally, customers just use the normal load balancer, and that is fine. The advanced features we try to introduce include many advanced features, for example, a blue-green deployment, load balancing to service based on header values, and many things, including JWT, but normally customers just use the basic load balancer. Most customers use TLS termination. Most customers use it, and they terminate the certificate at NGINX Ingress Controller level. NGINX Ingress Controller can do whitelisting, but they usually use a different product. For example, a Big-IP to do whitelisting instead of NGINX Ingress Controller. We have some projects integrating NGINX Ingress Controller with Prometheus including Grafana. The integration is working well, and there is no problem about that. Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller. I am totally satisfied with NGINX Ingress Controller if we talk about the functionality part. I think the price is acceptable, but the issue is not about the price. The issue is about the commonness. Load balancing and Ingress is some kind of generic use case, so there are no exciting features, such as an AI feature or something of that nature.
Python Developer and Application Analysts at All Solutions
Real User
Top 20
Jan 4, 2026
My advice for others looking into using NGINX Ingress Controller is that if you have a large number of users and need auto-scaling, you should definitely go with NGINX Ingress Controller, but if you are just starting out and are new, I would not recommend this. NGINX Ingress Controller is quite good. Its integration is really helpful, and customer support is also good as they usually connect us to the developer when needed, making it easy to get things done. I give this product a rating of nine out of ten.
NGINX Ingress Controller efficiently manages external access to services in Kubernetes, ensuring secure connection handling and traffic flow. Its robust architecture supports high availability, scalability, and performance, making it a vital component for managing ingress resources.NGINX Ingress Controller serves as a critical ingress point for Kubernetes clusters, offering vast customization options and seamless integration with NGINX and NGINX Plus. It provides enterprises with scalable...
NGINX Ingress Controller's governance and security features of AI capabilities are good, with all the basic guardrails available. The accuracy and reliability of NGINX Ingress Controller's AI capabilities are not 100%. Sometimes it hallucinates and requires more prompting to get what I want exactly, but overall it is a good feature that still needs improvements. NGINX Ingress Controller is a good tool to use. If you have a Kubernetes cluster, then it is easy to deploy and use, though you might face issues with the annotation part. I would give this review a rating of 9.
My advice to others looking into using NGINX Ingress Controller is to review the documentation first and ensure it serves your purpose. On a scale of one to ten, I rate NGINX Ingress Controller overall as a nine. I chose nine because I do not know the complete use case of the product, so I do not give it a perfect ten. That is my opinion, and while I have encountered some problems and hurdles, I have overcome all of them. It has worked very well for my purposes.
NGINX Ingress Controller is functional, but it is achievable and may take some extra time. The major issues typically relate to vulnerabilities, which F5 addresses with patches that require timely software upgrades to mitigate. I would rate this review a nine overall.
NGINX Ingress Controller as a reverse proxy itself, which I have already tested as a software as a standalone server and not just as an Ingress Controller, is perfect. As an Ingress Controller, it is doing fine. NGINX Ingress Controller must perform reverse proxy functions, path-based routing or host-based routing, and target which container to route traffic. It is deep technical work, but it is doing fine overall. Configuration is simple to start. To get deeper, I need to be a developer. Prometheus and Grafana are definitely necessary. The metrics I find really important is latency and request latency. That is one of the major metrics we love. I have configured a new use case once in my life when something required it to work. I did not test it again after that, just once in my life. Deployment works at small, medium, and large scales. I am working with different deployments. For the sales and pre-sales, I simplify the message as much as possible. The message for NGINX Ingress Controller is always complicated when delivered, and it requires simplification. I would rate this product 9 out of 10.
While I have not compared NGINX Ingress Controller with other solutions, I find all of its features, such as load balancing, security, and exposing multiple services behind one IP, to be the best facilities NGINX Ingress Controller is providing. We check all those aspects whenever we encounter any issues in production related to NGINX Ingress Controller. My advice for others looking into using NGINX Ingress Controller is that if you are using Google Cloud Platform, then you should definitely go with it as it is good.
I would like to see some AI capabilities, in-built AI capabilities in NGINX Ingress Controller to help with the load balancing. Normally, customers just use the normal load balancer, and that is fine. The advanced features we try to introduce include many advanced features, for example, a blue-green deployment, load balancing to service based on header values, and many things, including JWT, but normally customers just use the basic load balancer. Most customers use TLS termination. Most customers use it, and they terminate the certificate at NGINX Ingress Controller level. NGINX Ingress Controller can do whitelisting, but they usually use a different product. For example, a Big-IP to do whitelisting instead of NGINX Ingress Controller. We have some projects integrating NGINX Ingress Controller with Prometheus including Grafana. The integration is working well, and there is no problem about that. Currently, there is no suggestion about complexities or functions that can simplify my life with NGINX Ingress Controller. I am totally satisfied with NGINX Ingress Controller if we talk about the functionality part. I think the price is acceptable, but the issue is not about the price. The issue is about the commonness. Load balancing and Ingress is some kind of generic use case, so there are no exciting features, such as an AI feature or something of that nature.
My advice for others looking into using NGINX Ingress Controller is that if you have a large number of users and need auto-scaling, you should definitely go with NGINX Ingress Controller, but if you are just starting out and are new, I would not recommend this. NGINX Ingress Controller is quite good. Its integration is really helpful, and customer support is also good as they usually connect us to the developer when needed, making it easy to get things done. I give this product a rating of nine out of ten.