← Directory

Ingress NGINX

Ingress NGINX is a retired Kubernetes ingress controller for teams exposing cluster services, using NGINX as a reverse proxy and load balancer to route…

  • Development
  • Infrastructure
  • Network Services
  • Tools & Utilities
Ingress NGINX is a retired Kubernetes ingress controller for teams exposing cluster services, using NGINX as a reverse proxy and load balancer to route external traffic into services, with existing deployments, Helm charts, and container images remaining available but no further releases, bug fixes, or security updates planned.

Platform availability

Available on 1 of 9 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

25/100 Low

Maintained
0GitHub repository is archived
Popular
8619,458 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
07 serious findings, 4 minor, CI, tests, OpenSSF Scorecard 6.9/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
19,458
Open issues
348
Last commit
2026-03-19
Latest release
controller-v1.15.1
License
Apache-2.0
Activity
stale

Checked 16 days ago - source: GitHub (kubernetes/ingress-nginx)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Fill required settings first Set api_key, api_secret, ws_url (your LiveKit WebSocket address), and redis in your Ingress config before starting it. Without these, Ingress cannot connect to LiveKit or save session data, so it will not start correctly. source
  • Open the RTMP input port Set the RTMP TCP port in your config and make sure that port is reachable if you will push streams by RTMP. If it is closed, the RTMP server cannot receive your stream and the publish fails. source
  • Open the WHIP input port Set the WHIP port (a WebRTC way to push streams) and allow it from outside your host or container if needed. If that port is blocked, WHIP streamers cannot connect to start a stream. source
  • Retirement Ingress NGINX is retired: best-effort maintenance continues only until March 2026. Afterward there are no further releases, bugfixes, or security updates; existing deployments, Helm charts, and container images remain available but unmaintained. source
  • Retirement status Best-effort maintenance ended in March 2026; no further releases, bugfixes, or security updates are planned. source
  • Maintenance window Best-effort maintenance continued until March 2026. Afterward, no further releases, bugfixes, or security updates are planned, and existing deployments will not be broken. source

Fetched 4 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I debug an ingress-nginx controller container that keeps exiting or crashing?

Start an equivalent container running sleep 3600 and exec into it for further troubleshooting. This works around the controller process exiting or crashing, which makes the container hard to inspect.

How do I configure real-client-ip on a Kind or Minikube cluster installed with Helm?

Make a simple change to the service created by ingress-nginx. The host IP then becomes the real client IP address for curl requests sent from the host.

Why use ingress-nginx instead of exposing individual Kubernetes service ports?

ingress-nginx acts as an edge router or reverse proxy. It provides a single entry point instead of exposing individual service ports.

Where does the Ingress NGINX Controller store its configuration?

It is built around the Kubernetes Ingress resource and uses a ConfigMap to store the controller configuration.

Will existing deployments break when ingress-nginx stops receiving updates?

Existing deployments will not be broken, and existing Helm charts and container images will remain available. After March 2026 there will be no further releases, bug fixes, or security updates.

Answers sourced from discuss.kubernetes.io, kubernetes.github.io, kubernetes.github.io, kubernetes.github.io

Community

Collected yesterday - public community threads