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)
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
I like his lightware and potenza
What do you like best about the product?
His capacity to manage the ingress request based on content
What do you dislike about the product?
Is feel it's no son friendly that i espect.
What problems is the product solving and how is that benefiting you?
The básic balancer http kubernetics request to apps
It is especially well-suited for multi-cloud support you can cloud based enviroment.
What do you like best about the product?
1. Kubernet based
2. Cloud based
3. Cost saver
4.Security feature
What do you dislike about the product?
Feature to add large feature application in same device - may Orgnization save cost but adding & adding license in same device/box make device working enviroment more complex.
What problems is the product solving and how is that benefiting you?
Our enviroment is more stable post we remove Radware Solution !
Easilty Resouce available in market for F5 Technology !
A Robust and Reliable Solution for Kubernetes Traffic Management
What do you like best about the product?
F5 provides advanced traffic management features, ease of configuration, and robust security capabilities, making it a reliable solution for managing Kubernetes ingress traffic. As a professional user, I appreciate its efficiency and ease of use, as well as its ability to safeguard against potential attacks.
What do you dislike about the product?
When considering F5, it is important to weigh the benefits, such as advanced traffic management and security features, against potential downsides, such as its cost and complexity. While it is a reliable solution for managing Kubernetes ingress traffic, users may need to invest time and resources to learn and implement it effectively.
What problems is the product solving and how is that benefiting you?
F5 NGINX Ingress Controller addresses key business challenges by improving application availability, enhancing user experience, and strengthening security posture. Its advanced traffic management and security features help ensure the high availability and reliability of applications running on Kubernetes while protecting against potential attacks and data breaches. As a professional user, I recognize the value that F5 NGINX Ingress Controller can bring to businesses seeking to optimize their Kubernetes infrastructure.
F5 NGINX Ingress Controller is a popular used solution for managing ingress traffic.
What do you like best about the product?
High performance: F5 NGINX Ingress Controller is known for its high performance and scalability. It can handle high traffic loads with ease, making it ideal for large-scale applications.
Customizable: The controller is highly customizable, allowing users to configure it according to their specific needs. This flexibility makes it easy to integrate with various applications and infrastructure.
Easy to use: The F5 NGINX Ingress Controller comes with a user-friendly interface that simplifies the configuration process. The controller also supports automated deployment and configuration management, making it easy to deploy and manage ingress traffic.
Robust security features: The controller comes with a range of security features, including SSL/TLS termination, WAF, and DDoS protection. This ensures that your applications and infrastructure are secure and protected from potential threats.
What do you dislike about the product?
Complex installation: Setting up the F5 NGINX Ingress Controller can be a bit complex and may require some technical expertise. This can make it challenging for users who are new to Kubernetes or ingress management.
Limited community support: Unlike some other Kubernetes ingress controllers, the F5 NGINX Ingress Controller has a relatively small user community. This can make it challenging to find resources and support when troubleshooting issues.
Proprietary software: F5 NGINX Ingress Controller is a proprietary software, which means that users must pay for licensing and support. This can make it less accessible for smaller organizations or individuals.
What problems is the product solving and how is that benefiting you?
Complex installation: Setting up the F5 NGINX Ingress Controller can be a bit complex and may require some technical expertise. This can make it challenging for users who are new to Kubernetes or ingress management.
perfect Kubernetes Ingress Controller solution
What do you like best about the product?
Ease of use implementation set up and deployment
What do you dislike about the product?
I didn't like the way of API associations
What problems is the product solving and how is that benefiting you?
Routing the traffic for load balancing
