Smart traffic control has improved reliability and has protected critical APIs under heavy load
What is our primary use case?
My main use case for NGINX Ingress Controller is as a smart traffic controller, with the built-in firewalls, DoS protections for our APIs, and better reliability under load.
Whenever we need to manage traffic, we have contact with our tenants, so we create the hostname with their name and define a pod for them, allowing NGINX Ingress Controller to automatically scale the software and increase the number of pods when the number of users for this hostname increases, ensuring we don't lose traffic and the whole site doesn't go down.
Additionally, we can use advanced traffic and routing management, plus monitoring tools with their APIs. Whenever a site goes down or any error occurs, we receive instant error notifications through the API, which is really helpful.
What is most valuable?
In my experience, the best features NGINX Ingress Controller offers are its integration systems, which easily connect with other NGINX API gateways, risk limiting, JWT validations, and other NGINX products.
The integration with other analytics products enhances our team's capabilities as we use NGINX App Protect with NGINX Ingress Controller to protect the whole site using firewalls from denial of service, while the JWT validation helps protect our site from unauthorized access.
NGINX Ingress Controller has positively impacted our organization by saving us a lot of time. Previously, we used the NGINX open source ingress that lacked support and reliability, so when we switched to the official controller, it saved us time, reduced our downtime, and allowed for safe releases.
What needs improvement?
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.
For how long have I used the solution?
I have been using NGINX Ingress Controller for about one year.
What do I think about the stability of the solution?
NGINX Ingress Controller is quite stable in my experience.
What do I think about the scalability of the solution?
NGINX Ingress Controller's scalability is quite reliable and very easy to scale, as it mostly operates intelligently on its own without needing manual scalability.
How are customer service and support?
Customer support is very great and is one of the good points about NGINX Ingress Controller. I would rate customer support a ten because they are very helpful.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We previously used Traefik, which was very cheap, but it was not as powerful as NGINX Ingress Controller, so we switched.
What was our ROI?
I have seen a return on investment as mentioned. We saved about ten to fifteen engineering hours per month and a single outage annually.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was good. The pricing was expensive at first, but throughout the journey, it became feasible.
Which other solutions did I evaluate?
Before choosing NGINX Ingress Controller, we evaluated other options such as Amazon ALB Controller, Kong's ingress controller, and HAProxy, among others.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Nginx Ingress controller
What do you like best about the product?
it is easy to implemnt and control traffic based on use case and port like 443 (hhtps ) and http (80 ) and it support custom TCP port also . you can use nginx ingress controller on VM (IAAS ) based server and kuberneties (PAAS ) based servie also .
What do you dislike about the product?
by default it allow http 80 , it will good if it allow by default 443 due to security region .
What problems is the product solving and how is that benefiting you?
for this we have many option like for vm based appliction appchie , php and for gke based istio but Nginx work on both with intigration of php and other language also .
It provides variety of solution to meet the modern requirements
What do you like best about the product?
It provides solution with security and reliability keeping great performance
What do you dislike about the product?
The major downside of it being bit complex.
What problems is the product solving and how is that benefiting you?
It provides good scalability when it comes to providing load balance to the critical applications
#1 solution for Kubernetes management
What do you like best about the product?
Our company has been using the F5 INGINX ingress controller since many years for effective management of traffic for Kubernetes systems.
It is the best controller available in the market for traffic management.
The best part about this controller is that it is very easy to use as well as to implement.
It is also very useful to integrate with various other solutions. In case of any issues or concerns that we face as a customer we get the best customer support possible and instant support.
We have been using it on a daily basis and from time to time it also provides high realiability and sustainability.
What do you dislike about the product?
As an administrator I have been using this controller and working on this controller for many years.
I cannot think of any major issues of failures that you observed over the years and it has been a very stable solution.
There are no major drawbacks or points to dislike about this solution.
The cost of the controller is a little higher but it is worth the money.
What problems is the product solving and how is that benefiting you?
The F5 NGINX ingress controller is one of the best controller that are company realise on over the past years.
The best part about this controller is that it is very efficient for kubernetes traffic management and helps our kubernetes systems load balancing as well as efficient working.
It is very easy to use implement and integrate with various other solutions.
The best part about this controller is that it increases the stability sustainability robustness and reliability in kubernetes environments.
Solid and mature solution
What do you like best about the product?
The quality of the tool makes the ingress management more accessible and cleaner.
What do you dislike about the product?
The price could be expensive, especially for those who want to use it in a small scenario.
What problems is the product solving and how is that benefiting you?
The load balance is complex depending on the infrastructure, so with the solution, I could make the cluster management easier.
It's so amazing
What do you like best about the product?
User friendly, very easy. It's implementation is very easy
What do you dislike about the product?
It's not combatible with Cisco access points.
What problems is the product solving and how is that benefiting you?
Loadbalance
Amazing solution for Kubernetes traffic management
What do you like best about the product?
We have been using F5 NGINX Ingress controller for many years to efficiently manage the traffic in our Kubernetes systems.
Traffic management has never been so easier and precise as with the help of this controller.
The best part is that it is easy to use and implement. Also, it can be used to integrate with other solutions easily. In case of any issues. we get amazing customer support for any issues that we face.
We have been using it on a daily basis and due to the number of features that it provides, it is best for our company.
What do you dislike about the product?
I have been working as an administrator for many years and NGINX F5 Ingress controller is one of the best controller for traffic management for kubernetes systems.
The costing part of the controller is on a higher side but it is no as costly as many other counter parts present in the market.
There are no major drawbacks and dislikes about this product. It is best for traffic monitoring and management.
What problems is the product solving and how is that benefiting you?
We have been using F5 NGINX Ingress controller heaviloy for kubernetes traffic management.
It is the best solution for traffic monitoring and management.
It enhances the security and helps us achieve stability in our systems.
It increases the availability of kubernetes systems and sustainability.
It is very easy to implement and integrate with any other solutions.
Best Ingress Controller in the Indrustry
What do you like best about the product?
It reduced the complexity for kubernetes application traffic.
F5 Ingress Controller simplifies the management and optimization of traffic flow to your Kubernetes applications and provides advanced networking and security features to ensure the reliability and security of your applications
What do you dislike about the product?
It has limited community driven support and documentation, use-cases online are less available.
What problems is the product solving and how is that benefiting you?
It allows us to do load balancing on kubernetes cluster,ssl termination,traffic routing and auto scalling.
We are in perfect position with the help of this product which help us to serve our customers in cloud managed services, SaaS services etc.
Amazing product that i have felt
What do you like best about the product?
Great product,Cost management
Improve business process agility
Enhance decision making
Improve compliance & risk management
What do you dislike about the product?
So far nothing is seen the product with the faster support is expected
What problems is the product solving and how is that benefiting you?
Easy to use and the gui is best self explanatory to complete the configs
Best for Traffic Management
What do you like best about the product?
F5 NGINX Ingress controller is the best controller for traffic management. We have been using it for Kuberneted traffic management.
The best part about this controller is that it is very easy to implement and even easier to use on a daily basis.
It is best to handle high traffic loads and is highly reliable and sustainable. It is suitable for large scale applications and is highly customizable and can be easily integrated with other products.
We have been using it on a daily basis 24*7. We have never seen any major issue with this solution but from time to time we have received excellent customer support when ever needed.
What do you dislike about the product?
There are no major drawbacks in this product. It is highly useful for traffic management but its installation is comparatively complex for non-technical people or those who are new to traffic management.
I have not experienced any major issues or failures in the recent past though we have been using it from many years.
Costing part is a little higher but it is worth the features it provides.
What problems is the product solving and how is that benefiting you?
F5 NGINX Ingress controller is best for Kubernetes traffic management and provides us with various benefits.
It is very easy to use and integrate with other solutions.
It is best for kubernetes and enhances security.
Brings in stability and sustainability in the organisation
It increases the availability and is robust.
