With NGINX Ingress Controller 5.8, you can limit how many requests each client has open at once, install the Helm chart in a cluster with no internet access, and pass user details from your authentication service to your backends. The connection limits and the authentication headers are policies you set without snippets, and they replace two Ingress-NGINX annotations.
On the operations side, NGINX keeps up with rolling deployments on busy clusters, DNS records work with current ExternalDNS releases, and the images ship NGINX Open Source 1.31.9. Changes that need an F5 NGINX Enterprise solution, including JSON Web Token (JWT) claim authorization for F5 NGINX Plus and labels for F5 NGINX One Console, are collected in one section at the end. Two changes in behavior are listed under upgrade notes. The details follow, starting with connection limits.
Release highlights
- Connection limits: Limit how many requests each client can have open at once.
- Offline Helm installs: Install and upgrade in clusters with no internet access.
- Auth response headers: Pass user details from your authentication service to your backends.
- Reloads that keep pace with rolling deployments: Keep traffic going to the right pods during a rollout, even on a busy cluster.
- Stability and bug fixes: Updates to Ingress request headers, ExternalDNS support, and the bundled NGINX Open Source version.
Connection limits for Ingress and VirtualServer resources
What’s new: A new connection limit policy works on a VirtualServer, a single route, or an Ingress. By default it limits each client IP address, and it can also limit by header, cookie, or request path, or set one total for a whole resource. A dry-run mode logs the requests it would reject, so you can try a limit before you enforce it (API and validation nginx/kubernetes-ingress#11216, VirtualServer and VirtualServerRoute nginx/kubernetes-ingress#11218, Ingress nginx/kubernetes-ingress#11222).
Why it matters: One busy client, or a sudden spike, can’t use up every connection a backend has. If you’re moving from Ingress-NGINX, this replaces its limit-connections annotation.
Helm installs without network access
What’s new: The Helm chart now includes everything it needs to check your values, so helm install and helm upgrade work in clusters that can’t reach the internet. Before, the chart downloaded schema files from GitHub during every install. Started by community contributor sathieu (nginx/kubernetes-ingress#9016) and finished by the team (nginx/kubernetes-ingress#11364).
Why it matters: Air-gapped and firewalled clusters can install and upgrade with full values validation, so a typo still fails before it reaches the cluster.
Auth response headers for your backends
What’s new: ExternalAuth policies can now forward headers from your authentication service’s response, such as the user name and email OAuth2 Proxy returns. List the headers on the policy, and NGINX copies them into each request it forwards. A client can’t set those headers itself (nginx/kubernetes-ingress#11423).
spec:
externalAuth:
authURI: /oauth2/auth
authServiceName: oauth2-proxy-svc
authResponseHeaders:
- X-Auth-Request-User
- X-Auth-Request-Email
Why it matters: Your backends get the user and tenant details your authentication service already checked, without parsing tokens or adding snippets. If you’re moving from Ingress-NGINX, this replaces its auth-response-headers annotation.
Reloads that keep pace with rolling deployments
What’s new: NGINX Ingress Controller could hold back a reload for minutes while it waited for a quiet moment, so NGINX kept sending traffic to pods that had already stopped. Now it applies pending changes at least every two seconds, and you can tune that window (nginx/kubernetes-ingress#11001).
Why it matters: During a rolling deployment, NGINX follows your pods within seconds, even when the rest of the cluster is busy. A shorter reload window means faster updates, and a longer one means fewer reloads.
Smaller enhancements
- NGINX variables in Ingress request headers: The
nginx.org/proxy-set-headersannotation now accepts NGINX variables, such as the client address or a cookie value, as VirtualServer resources already did (nginx/kubernetes-ingress#11151). - NGINX Open Source 1.31.9 in the images: Up from NGINX Open Source 1.31.7 in NGINX Ingress Controller 5.7.0.
Stability and bug fixes
- DNS records work with ExternalDNS 0.21 and later: A new setting picks which ExternalDNS API NGINX Ingress Controller writes VirtualServer records to, and the default keeps existing setups as they are (nginx/kubernetes-ingress#11121).
Upgrade notes
Before upgrading to NGINX Ingress Controller 5.8, please verify your normal application behavior does not rely on any of the items below:
- Pending reloads apply at least every two seconds: On a busy cluster, NGINX may now reload more often than before. To turn the window off, set
-batch-reload-windowor thecontroller.batchReloadWindowHelm value to0(nginx/kubernetes-ingress#11001). - ExternalDNS needs its CRD installed for the controller to start: If you use ExternalDNS with NGINX Ingress Controller, install the CRD for the DNSEndpoint API it writes to before you upgrade, or the controller exits at startup (nginx/kubernetes-ingress#11121).
Community recognition
Thank you to everyone who investigated issues, proposed patches, or tested NGINX Ingress Controller 5.8.
Community contributions
One community member started the offline Helm chart installs in NGINX Ingress Controller 5.8, credited above. Thanks to sathieu!
Community inspired development work
The batch reload changes were inspired by an earlier effort, credited in the team’s PR: wd‘s earlier implementation, which set out to stop reloads for changes that touch only endpoints. Your work gave us a place to start.
Send a pull request for NGINX Ingress Controller 5.9
Find something to work on in the open issues, or start from a bug you’ve hit or a feature you need. The contributing guide explains the process, from opening a discussion to sending a pull request.
Also in this release: Features that need an F5 NGINX Enterprise solution
These changes need NGINX Plus, F5 WAF for NGINX, or NGINX One Console.
- JWT claim authorization: JWT policies on VirtualServer and VirtualServerRoute resources can check a token’s claims, such as a user’s roles, before a request reaches your backend, and pass claims on as headers (API and validation nginx/kubernetes-ingress#11225, configuration nginx/kubernetes-ingress#11226, NGINX Plus template nginx/kubernetes-ingress#11227, design nginx/kubernetes-ingress#11187, examples nginx/kubernetes-ingress#11224, annotation variables nginx/kubernetes-ingress#11151).
- NGINX Plus endpoint updates continue during batches: Endpoint changes keep reaching NGINX Plus through its API while other changes wait, so busy clusters reload less often (nginx/kubernetes-ingress#11001).
- Labels from
nginx-agent.confreach NGINX One Console: Labels you set for NGINX Agent now show up in NGINX One Console, and the Helm chart can set them (nginx/kubernetes-ingress#11346, nginx/kubernetes-ingress#11347). - NGINX Plus R37.3 and F5 WAF for NGINX 5.16.2: The NGINX Plus images move up from NGINX Plus R37.2 in NGINX Ingress Controller 5.7.0, and ship F5 WAF for NGINX 5.16.2.
Getting started with NGINX Ingress Controller 5.8
NGINX Ingress Controller 5.8 is available now as container images on Docker Hub, GitHub Container Registry (ghcr.io), Amazon ECR Public Gallery, and Quay.io, and as version 2.9.0 of the Helm chart on ghcr.io.
- Release notes and changes: Read the full changelog.
- Install and upgrade: Follow the NGINX Ingress Controller installation guide.
- Documentation: Visit the NGINX Ingress Controller documentation.
- Moving from Ingress-NGINX? Follow the NGINX Ingress Migration Tool guide.
- Interested in NGINX’s open source Kubernetes ecosystem? Start at kubernetes.nginx.org.
For more release announcements and technical articles, see the NGINX Blog.
Compatibility
NGINX Ingress Controller 5.8 is compatible with these versions:
- Kubernetes: 1.35 through 1.37
Keeping NGINX Ingress Controller up to date
We recommend running the latest version of NGINX Ingress Controller, since each release includes fixes and improvements. NGINX Ingress Controller 5.8 ships NGINX Open Source 1.31.9 and NGINX Plus R37.3, which include the NGINX security fixes in F5’s November 18, 2026 security notification.
To stay informed, subscribe to F5 notifications and select the relevant advisory updates.


