NGINX Gateway Fabric 2.9: API key, TLS renewal without reload and TCP/UDP snippets
NGINX Gateway Fabric 2.9 released: API key authentication, TLS certificate rotation without reload and support for Nutanix Kubernetes Platform.
UptimeMag editorial team · 20 November 2026 · 2 min read

NGINX released NGINX Gateway Fabric version 2.9 on 20 November 2026, the open-source project that implements the Kubernetes Gateway API using NGINX as the data plane. For teams running Kubernetes clusters behind an NGINX gateway rather than a simple Ingress, the release introduces features that directly impact security and day-to-day operations: API key authentication, TLS certificate rotation without interruption, and snippet-based configuration for TCP/UDP traffic as well.
Main features
The most visible addition is API key authentication: a new AuthenticationFilter of type APIKey lets you protect a route so that only requests carrying a valid key—sent via header or query string—pass through. Keys are stored in a per-client Secret, so revoking access to a customer means editing a single row. Keys passed via URL are excluded from the access log.
TLS certificate handling has also changed: when cert-manager renews a certificate on a listener, NGINX Gateway Fabric applies the new certificate without reloading NGINX. On a Gateway with many listeners, this means no more periodic reloads for scheduled renewals.
SnippetsPolicy rules, previously limited to HTTP, can now be attached to TCP and UDP traffic on a Gateway as well—useful for setting parameters like proxy_timeout when the native API doesn't cover them.
On the security front, three changes restrict Secret access from the control plane: you can now limit the namespaces being read, set label selectors via Helm, and the control plane no longer loses provisioning state after a restart.
Finally, NGINX Gateway Fabric joins the Nutanix Kubernetes Platform Partner Catalog, starting from version 2.8.0 tested on NKP 2.18 with Kubernetes 1.35. NKP 2.18 was released on 2 July 2026 and brings full support for Kubernetes 1.35, containerd v2, Rocky Linux 9.7, and Flatcar LTS.
Before you upgrade
Teams upgrading to 2.9 must first install Gateway API CRDs 1.7.0: the default path for session cookies changes (now /) and the field for the cookie name moves to sessionPersistence.cookie.name. Anyone using session persistence with existing configurations needs to review both parameters before switching to the new version.
The container image and Helm chart are available on GitHub Container Registry (ghcr.io); the changelog and installation guide are in the official project repository.
Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).