API key authentication is new in NGINX Gateway Fabric 2.9: protect a route so only clients with a valid key reach your service. Renewed TLS certificates now take effect without reloading NGINX, and snippets can now configure TCP and UDP traffic. TLS traffic can be split across weighted backends, upstream memory zones can size themselves, and NGINX Gateway Fabric is now in the Nutanix Kubernetes Platform Partner Catalog.
NGINX Gateway Fabric 2.9 also changes how the control plane runs: it can read Secrets in only the namespaces you choose, and it recovers on its own from failed configuration updates. The move to Gateway API 1.7 renames a session persistence field and changes a default, so read the upgrade notes before you move to NGINX Gateway Fabric 2.9. Configurable failure behavior for F5 AI Guardrails and a fix for F5 WAF for NGINX policy bundles from F5 NGINX Instance Manager need an F5 NGINX Enterprise solution, and they’re collected in one section at the end.
Release highlights
- API key authentication: Protect a route with a key for each client.
- Available on Nutanix Kubernetes Platform: Install NGINX Gateway Fabric from its Partner Catalog.
- TLS certificate updates without reloads: Renew certificates without reloading NGINX.
- Snippets for TCP and UDP traffic: Use snippets for TCP and UDP traffic, as you already can for HTTP.
- Least-privilege access to Secrets: Limit which namespaces the control plane reads Secrets from.
- Stability and bug fixes: Updates to session persistence, the inference endpoint picker, recovery from failed updates, route status, and the Helm chart.
API key authentication for your routes
What’s new: AuthenticationFilter can now require an API key. Store each client’s key in a Secret, attach the filter to a route, and only requests that send a valid key, in a header or a query parameter, get through. Keys sent in the URL are kept out of the access log (nginx/nginx-gateway-fabric#6141).
apiVersion: gateway.nginx.org/v1alpha1
kind: AuthenticationFilter
metadata:
name: api-key-auth
spec:
type: APIKey
apiKey:
secretRef:
name: api-keys
sources:
- type: Header
name: X-API-Key
- type: Query
name: api_key
Why it matters: You can protect an API without running an identity provider. Each client has its own key, so you can grant or revoke a client’s access by editing one line of the Secret.
TLS certificate updates without reloads
What’s new: When a listener’s certificate changes, for example when cert-manager renews it, NGINX Gateway Fabric now applies the new certificate without reloading NGINX (nginx/nginx-gateway-fabric#6163).
Why it matters: On a Gateway with many listeners, scheduled cert-manager renewals no longer reload NGINX.
Snippets for TCP and UDP traffic
What’s new: SnippetsPolicy can now add NGINX configuration to the TCP and UDP traffic a Gateway handles, not just HTTP traffic. Attach the policy to a Gateway (nginx/nginx-gateway-fabric#6061).
apiVersion: gateway.nginx.org/v1alpha1
kind: SnippetsPolicy
metadata:
name: stream-timeouts
spec:
targetRefs:
- group: gateway.networking.k8s.io
kind: Gateway
name: gateway
snippets:
- context: stream
value: "resolver_timeout 10s;"
- context: stream.server
value: "proxy_timeout 7s;"
Why it matters: When you need a TCP or UDP setting NGINX Gateway Fabric has no API for, such as a proxy timeout, you can set it on the Gateway itself.
Least-privilege access to Secrets
What’s new: Three changes narrow which Secrets the control plane reads:
- Secrets only from the namespaces you choose: Set the namespaces from the Helm chart. Developed by community contributor mzimry (nginx/nginx-gateway-fabric#6180).
- The Secret label selector in the Helm chart: The label selector from NGINX Gateway Fabric 2.8 now has a Helm value. Thanks to community contributor dollarsmoney for this change (nginx/nginx-gateway-fabric#6179).
- The control plane’s own Secrets no longer need the label: Provisioning works after a restart (nginx/nginx-gateway-fabric#6236).
Why it matters: On a shared cluster, the control plane only reads the Secrets your Gateways need, not every team’s.
Available on Nutanix Kubernetes Platform
What’s new: NGINX Gateway Fabric is now listed in the Nutanix Kubernetes Platform Partner Catalog. The listing starts with NGINX Gateway Fabric 2.8.0, tested on Nutanix Kubernetes Platform 2.18 with Kubernetes 1.35, and new releases follow (catalog listing nutanix-cloud-native/nkp-partner-catalog#86, nginx/nginx-gateway-fabric#6178).
Why it matters: If you run Nutanix Kubernetes Platform, you can install and upgrade NGINX Gateway Fabric from the catalog you already use.
Upstream zones that size themselves
What’s new: Set the upstream memory zone size to auto, and NGINX Gateway Fabric sizes each zone to fit the endpoints behind it, growing it as an upstream gains endpoints and shrinking it as the upstream gets smaller (nginx/nginx-gateway-fabric#5979).
Why it matters: You no longer pick one size that has to fit your largest upstream, which wastes memory on small ones and still fails when an upstream outgrows it.
Weighted traffic splitting for TLSRoutes
What’s new: TLSRoutes can now split connections across several backends by weight, as HTTPRoutes and GRPCRoutes already can, whether NGINX terminates TLS or passes it through (nginx/nginx-gateway-fabric#6062).
Why it matters: You can run canary and blue-green rollouts for TLS services by shifting weights.
Smaller enhancements
- Gateway API 1.7.0: NGINX Gateway Fabric now supports Gateway API 1.7.0, which adds a cookie path setting for session persistence. Two session persistence changes are in upgrade notes (nginx/nginx-gateway-fabric#6191).
- Gateways and listeners as maps in the Helm chart: You can now define gateways and listeners as maps, so a values file can override one setting without repeating the whole list. Community contributor owaisaamir built this (nginx/nginx-gateway-fabric#6002).
- Labels and annotations on the data plane ServiceMonitor: Add your own labels and annotations, so Prometheus setups that select ServiceMonitors by label can find it (nginx/nginx-gateway-fabric#6209).
- NGINX Open Source 1.31.9 in the data plane: Up from NGINX Open Source 1.31.7 in NGINX Gateway Fabric 2.8.0.
Stability and bug fixes
- Failed configuration updates are retried: If NGINX rejects a configuration, the control plane keeps retrying it, and the Gateway reports the failure until a retry succeeds (nginx/nginx-gateway-fabric#6039).
- A data plane container restarts when NGINX stops: Kubernetes restarts it instead of leaving it serving out-of-date configuration (nginx/nginx-gateway-fabric#6160).
- One unresponsive data plane no longer blocks configuration updates: NGINX Agent v3.12.4 fixes a hang that stopped all later updates when one agent didn’t respond (nginx/nginx-gateway-fabric#5774).
- A native endpoint picker module for Gateway API Inference Extension: NGINX now reports back to the endpoint picker on every request, and large inference requests no longer exceed its size limit (nginx/nginx-gateway-fabric#6083).
- Data plane pods get their configuration when a webhook rewrites the image: Registry mirror webhooks no longer leave pods without configuration. This fix comes from community contributor somaz94 (nginx/nginx-gateway-fabric#6193).
- TLSRoutes keep their hostnames when listeners share one across ports: A TLSRoute attached to one of those listeners lost its hostnames, so NGINX Gateway Fabric closed its connections. Community contributor somaz94 also wrote this fix (nginx/nginx-gateway-fabric#6182).
- Routes attach when a ListenerSet reuses a Gateway listener name: If a route was attached to the whole Gateway, NGINX Gateway Fabric dropped it and left its status empty. Developed by community contributor locker95 (nginx/nginx-gateway-fabric#6237).
- Routes report a backend with no ready endpoints: HTTPRoutes and GRPCRoutes now show when a backend has nothing ready to serve traffic (nginx/nginx-gateway-fabric#6093).
- Load balancer hostnames stay in the Service status: A hostname from a load balancer controller, such as the AWS Load Balancer Controller, is kept alongside a Gateway’s static IP address (nginx/nginx-gateway-fabric#6125).
- Successful updates are logged only when configuration is sent: The control plane logged a successful update even when the configuration hadn’t changed and it sent NGINX nothing. Thanks to community contributor SidharathBansal for this fix (nginx/nginx-gateway-fabric#5875).
- Helm annotations with a colon render correctly: An annotation value such as
owner: platform-teambroke the NginxGateway or GatewayClass resource that the chart rendered. Community contributor Alja9 built this (nginx/nginx-gateway-fabric#6113).
Under the hood
- Status updates are written in the background: The control plane no longer waits on each status write (nginx/nginx-gateway-fabric#6166).
- Product telemetry counts AccessPolicies: Telemetry now reports how many AccessPolicies target Gateways and routes (nginx/nginx-gateway-fabric#6218).
Upgrade notes
Before upgrading to NGINX Gateway Fabric 2.9, please verify your normal application behavior does not rely on any of the items below:
- Upgrade Gateway API to 1.7.0 first: Install the Gateway API 1.7.0 CRDs before you upgrade NGINX Gateway Fabric (nginx/nginx-gateway-fabric#6191).
- Session persistence cookies default to the
/path: If your routes relied on the cookie being scoped to their own path, setsessionPersistence.cookie.path(nginx/nginx-gateway-fabric#6191). - The session cookie name moves to
sessionPersistence.cookie.name: Update configurations that setsessionPersistence.sessionName(nginx/nginx-gateway-fabric#6191).
Community recognition
NGINX Gateway Fabric is built in the open, and every release carries work from people outside the team. Whether you sent a pull request, tested a fix, or helped shape a feature, thank you!
Community contributions
If you upgrade to NGINX Gateway Fabric 2.9, you’ll be running work from seven community members: a namespace-scoped Secret watch, two Helm chart enhancements, and five bug fixes. Each is credited above, next to the change it made. Our thanks to Alja9, dollarsmoney, locker95, mzimry, owaisaamir, SidharathBansal, and somaz94!
Contribute to NGINX Gateway Fabric 2.10
The contributing guide is the place to start, from opening a discussion to sending a pull request. From there, pick up an open issue, fix a bug you’ve run into, or build a feature you need.
Also in this release: Features that need an F5 NGINX Enterprise solution
These changes need F5 NGINX Plus, F5 AI Guardrails, F5 WAF for NGINX, F5 NGINX One Console, or F5 Policy Lifecycle Manager.
- Configurable failure behavior for F5 AI Guardrails: Choose whether a request is rejected or allowed through when F5 AI Guardrails can’t return a verdict (nginx/nginx-gateway-fabric#6158).
- NGINX Plus R37.3 and F5 WAF for NGINX 5.16.2: The NGINX Plus data plane images ship both.
- F5 WAF for NGINX policy bundles from NGINX Instance Manager stay current: NGINX Gateway Fabric now picks the bundle built with NGINX Instance Manager’s active compiler, not an older one (nginx/nginx-gateway-fabric#6188).
- Fewer Secrets to label with a Secret label selector: With
--watch-secret-label-selectorset, the NGINX Plus license, CA, and client SSL Secrets, and the NGINX One Console dataplane key, no longer need the label. Only Policy Lifecycle Manager storage Secrets outside the control plane’s namespace still do (nginx/nginx-gateway-fabric#6236).
Getting started with NGINX Gateway Fabric 2.9
NGINX Gateway Fabric 2.9 is available now as a container image and a Helm chart on GitHub Container Registry (ghcr.io).
- Release notes and changes: Read the full changelog.
- Install and upgrade: Follow the NGINX Gateway Fabric installation guide.
- Documentation: Visit the NGINX Gateway Fabric documentation.
- Moving Ingress resources to Gateway API? Convert them with ingress2gateway, which has providers for NGINX Ingress Controller, Ingress-NGINX, and other Ingress controllers.
- 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 Gateway Fabric 2.9 is compatible with these versions:
- Kubernetes: 1.35 through 1.37
- Gateway API: 1.7.0
- Gateway API Inference Extension: 1.6.2
Keeping NGINX Gateway Fabric up to date
We recommend running the latest version of NGINX Gateway Fabric, since each release includes fixes and improvements. NGINX Gateway Fabric 2.9 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.


