NGINX Ingress Controller

Rating: 7 out of 10

Incentivized

March 27, 2024

Use Cases and Deployment Scope

Need a light weight ingress controller to manage incoming traffic for container workloads.

Pros

Provide access to containers
Manage traffic
Route traffic
Lightweight
Near to zero downtime

Cons

Is a little complex
Ability to manage certificates
Service discovery

Likelihood to Recommend

Is a high performance, light weight load balancer that is designed specifically to support container platforms!

Verified User

Engineer in Information Technology (1001-5000 employees)

Vetted Review

4 years of experience

NGINX Ingress

Rating: 10 out of 10

Incentivized

March 22, 2024

Use Cases and Deployment Scope

We are using at on AWS EKS. In microservices architecture its help us to create a zero trust architecture and mTLS for app security.
We have 50+ of microservices. To manage traffic between them we are using nginx ingress controller. Its easy to install and have better performace with minimal resources consumption.

Pros

To manage external traffic Nginx ingress provides us a single point of traffic entry instead of using AWS LB for every service. Along with saving cost its also help us to create and manage access to our application
Flexible NGINX Ingress allows us to easily customize and extend its functionality using annotation ,ConfigMaps and custom Templates
It has extensive and active community support

Cons

Its not related to Ingress functionality but certificate management with cloud vendor would be a feature i would like to see.

Likelihood to Recommend

Best suited if we have to manage external traffic inside your kubernetes cluster and want to use granular control to your applications.

Amit Setia

Senior Engineer] in Engineering at Rakuten Viki (51-200 employees)

Vetted Review

2 years of experience