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.
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.
