Information Security Engineer at a outsourcing company with 1,001-5,000 employees
Reseller
Top 20
Mar 12, 2026
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.
Python Developer and Application Analysts at All Solutions
Real User
Top 20
Jan 4, 2026
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.
Container Management is essential for efficiently deploying and maintaining applications in microservices architectures, enhancing scalability and reliability.This practice involves orchestrating containerized applications to optimize resources and streamline application lifecycle management. Users gain improved control over infrastructure, enabling faster deployment cycles and simplification of complex cloud-native operations. Popular solutions offer automated updates, clustering, and...
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.
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.