NGINX Ingress Controller
docs.nginx.com
- Free plan
- Self-hosted
What NGINX Ingress Controller is
NGINX Ingress Controller is a self-hosted Kubernetes Ingress Controller that load balances WebSocket, gRPC, TCP, and UDP applications. It supports content-based routing and TLS/SSL termination, with further NGINX settings configurable through annotations and ConfigMaps. Manifest installation offers Deployment, DaemonSet, or StatefulSet modes. Its policy resources cover access control, rate limiting, API keys, authentication, mTLS, WAF, CORS, and HSTS, though some policies require NGINX Plus. The Plus version adds real-time metrics, more load-balancing methods, session persistence options, active health checks, and JWT validation. The controller can expose NGINX and controller metrics in Prometheus format, including through a ServiceMonitor with Prometheus Operator. Documented integrations include F5 WAF for NGINX, F5 DoS for NGINX, F5 BIG-IP, cert-manager, ExternalDNS, Prometheus, Istio, Linkerd, and Open Service Mesh. The free option uses NGINX Open Source and requires a Kubernetes cluster. Plus requires a subscription and JWT or certificate credentials for registry access. F5 recommends encrypting Kubernetes Secrets at rest and least-privilege RBAC, noting that the default ServiceAccount can access all cluster Secrets.
Who it suits
It suits teams operating Kubernetes clusters that need ingress routing and load balancing for the listed application protocols. Teams considering Plus features or production support should review the stated subscription and support conditions.
Good to know, and what to watch
- Supports WebSocket, gRPC, TCP, and UDP applications.
- Offers Deployment, DaemonSet, and StatefulSet modes.
- Exposes metrics in Prometheus format.
- Policy resources include rate limiting and authentication.
- Free option uses NGINX Open Source.
- A Kubernetes cluster is required.
- Some policies require NGINX Plus.
- Default ServiceAccount can access all cluster Secrets.
- Read-only root filesystem is not enabled by default.
Plans
Every plan and priceNGINX Plus Ingress Controller
NGINX Ingress Controller with NGINX Open Source
Free plan
The verdict
NGINX Ingress Controller offers a self-hosted ingress option with routing, TLS termination, and a broad policy set. Cluster configuration and the distinction between Open Source and Plus capabilities are important considerations.
What the maker publishes
- Deployment choices
- Manifest installation supports Deployment, DaemonSet, or StatefulSet deployment modes. source
- Integrations
- Documented integrations include F5 WAF for NGINX, F5 DoS for NGINX, F5 BIG-IP, cert-manager, ExternalDNS, Prometheus, Istio, Linkerd, and Open Service Mesh. source
- Maker
- F5 lists its headquarters as Seattle, Washington, and its founding year as 1996. source
- NGINX Plus features
- NGINX Plus adds real-time metrics, additional load-balancing methods, session persistence options, active health checks, and JWT validation. source
- Plus licensing telemetry
- NGINX Plus requires a JWT for subscription validation and reports usage telemetry by default every hour and when NGINX is reloaded. source
- Prometheus
- The controller can expose NGINX and controller metrics in Prometheus format, including through a ServiceMonitor when using Prometheus Operator. source
- Purpose
- NGINX Ingress Controller is a Kubernetes Ingress Controller that load balances WebSocket, gRPC, TCP, and UDP applications. source
- Read-only filesystem
- A read-only root filesystem is recommended to reduce attack surface but is not enabled by default. source
- Release support
- The maker says each annual Long-Term Support release is supported for up to three years and receives security and stability bug fixes. source
- Routing and TLS
- It supports content-based routing and TLS/SSL termination, with additional NGINX features configurable through annotations and ConfigMaps. source
- Security guidance
- The maker recommends encrypting Kubernetes Secrets at rest and documents least-privilege RBAC, while noting the default ServiceAccount can access all Secrets in the cluster. source
- Security policies
- Policy resources include access control, rate limiting, API keys, authentication, mTLS, WAF, CORS, and HSTS options, with some policies requiring NGINX Plus. source
- Support
- Technical support applies to provider-supported Kubernetes platforms that pass Kubernetes conformance tests; F5 customer support covers the latest controller version and versions released within two years of the current release. source
Checked against the maker's pages on 30 Sept 2026.