Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

NGINX Ingress Controller review

Freemium#2 of 28 in Kubernetes Ingress Controllers

A free, self-hosted controller for routing, TLS, traffic policies, and edge integrations.

9.2/10Editor score
Visit NGINX
NGINX Ingress Controller9.2 Visit NGINX

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

NGINX Ingress Controller is a Kubernetes controller for NGINX and NGINX Plus, designed for platform teams and operators managing application traffic at the cluster edge. It runs inside a Kubernetes cluster and routes HTTP applications using content-based and path-based rules, while also load-balancing WebSocket, gRPC, TCP, and UDP traffic. TLS/SSL termination, authentication and authorization policies, request rate limiting, and NGINX-specific VirtualServer resources extend its coverage beyond basic HTTP routing.

The open-source controller is available as a free plan, while NGINX Plus adds commercial features through a subscription. Configuration can use standard Kubernetes Ingress resources, annotations, ConfigMaps, and VirtualServer or VirtualServerRoute custom resources. Its ecosystem fit is strongest for teams already operating Kubernetes and NGINX: integrations include Kubernetes, NGINX Plus, F5 WAF for NGINX, cert-manager, and Prometheus. cert-manager support covers certificate management for VirtualServer resources, and F5 WAF for NGINX policy integration adds a path to web application firewall controls.

Traffic-management features are a notable strength. Canary and blue-green routing support controlled delivery patterns, while rate limiting and policy-based authentication address common edge requirements. The controller also covers both HTTP and non-HTTP traffic through TCP and UDP load balancing. Teams should choose it when they want an open-source, self-hosted NGINX-based ingress layer with these capabilities. It is less suitable for organizations seeking a managed deployment or a broader verified API model beyond Ingress, and teams requiring NGINX Plus commercial features should plan for its subscription model.

NGINX Ingress Controller pros and cons

  • Where it wins
    • Free open-source controller for self-hosted Kubernetes deployments
    • Supports routing, TLS, canary, blue-green, rate limiting, and auth policies
    • Integrates with NGINX Plus, F5 WAF for NGINX, cert-manager, and Prometheus
  • Where it doesn't
    • Requires a Kubernetes environment and operator-managed deployment
    • NGINX Plus commercial features require a subscription
    • Its verified ingress API model is centered on Ingress

NGINX Ingress Controller fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update