NGINX Ingress Controller 5.8: connection limits, auth headers and offline Helm
F5 releases NGINX Ingress Controller 5.8: per-client connection limits, auth response headers forwarding to backends, and air-gapped Helm chart installation.
UptimeMag editorial team · 20 November 2026 · 2 min read

F5 released NGINX Ingress Controller version 5.8 on 20 November 2026, with a new policy to limit connections per client, forwarding of headers from authentication service responses to backends, and installation of the Helm chart in clusters without internet access.
Three major new features
The connection limit policy works on VirtualServer resources, individual routes or Ingress. By default it limits per client IP address, but can also limit by header, cookie or request path, or set a total limit for the entire resource. A dry-run mode is available that logs requests that would be rejected, useful for testing the limit before activating it.
ExternalAuth policies can now forward to backends the headers returned by the authentication service, for example username and email that OAuth2 Proxy adds to the response. Headers to forward are listed in the policy's authResponseHeaders field; a client cannot set them directly.
The Helm 2.9.0 chart now includes everything needed to validate values without downloading schema from GitHub during each installation, a requirement for air-gapped clusters or those behind restrictive firewalls.
Additionally, there is a fix for reloads: previously the controller could delay a reload for minutes waiting for a quiet moment, continuing to send traffic to already-terminated pods. Now it applies pending changes at least every two seconds, with a configurable window via -batch-reload-window or the controller.batchReloadWindow Helm value.
Why the two policies "replace" ingress-nginx
The two new policies (connection limit and auth response headers) replace the limit-connections and auth-response-headers annotations from the community kubernetes/ingress-nginx project respectively. This is no accident: the community controller reached end of life on 24 March 2026, when Kubernetes archived the ingress-nginx repository, four months after the retirement announcement on 11 November 2025, and F5's NGINX Ingress Controller project, maintained in a separate repository, remains the most direct migration path for those leaving the retired controller.
Versions and compatibility
| NIC Version | Tested Kubernetes | Helm chart | NGINX / NGINX Plus |
|---|---|---|---|
| 5.8.0 | 1.30 - 1.37 | 2.9.0 | 1.31.9 / R37.3.0.1 |
| 5.7.1 | 1.30 - 1.37 | 2.8.1 | 1.31.8 / R37.2.0.1 |
Version 5.7 was released on 15 October 2026, so the jump to 5.8 arrives after approximately five weeks.
Upgrade notes
Those using ExternalDNS must install the CRD for the DNSEndpoint API before upgrading: without it, the controller will not start. The 5.8 images include NGINX security fixes from the F5 advisory dated 18 November 2026; to stay updated it's advisable to subscribe to F5 security notices.
The controller is available on Docker Hub, GitHub Container Registry, Amazon ECR Public Gallery and Quay.io; the Helm chart is published as version 2.9.0 on ghcr.io.
Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).