Reliability has supported AI gateway routing and currently secures LLM traffic with flexible policies
What is our primary use case?
I am currently working with NGINX Ingress Controller but in a different perspective than before. We haven't used App Protect anymore, but as an implementer, we use it as a front end for an AI gateway to do some mapping for certain information before sending the LLM request to the AI gateway.
NGINX Ingress Controller itself is a reverse proxy, so we manipulate some requests. We utilize NGINX Ingress Controller to manipulate some requests prior to the AI gateway.
My use case has changed because nowadays the main focus for use cases are for AI and AI security that mainly focuses on LLM security.
What is most valuable?
A third-party solution would be better for that. NGINX Ingress Controller is a software, so its capability of working is fitting inside the organization, not facing the internet. The one that faces the internet is something else, for example, the firewall or Big-IP, so normally we do the whitelisting at those levels, not the NGINX Ingress Controller layer.
Most customers are satisfied with the reverse proxy capability, but the main issue is that the Ingress NGINX, the one that is most widely used, will be deprecated this month. I think that is the main concern from the customer side, but normally NGINX Ingress Controller just works well and is reliable.
From my experience, I think the main benefit NGINX Ingress Controller provides to the end user is the reliability of NGINX Ingress Controller itself. The customer can rely on this service that it will work well, and there will be no problem or issue that they need to concern.
What needs improvement?
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.
For how long have I used the solution?
I have been working with NGINX Ingress Controller for approximately seven years.
How was the initial setup?
I think the initial setup process for NGINX Ingress Controller is simple.
What other advice do I have?
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.
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
