The Kubernetes SIG Network community has unveiled Gateway API v1.5, released on February 27, 2026. This version is the largest to date, focusing on transitioning widely requested experimental features to the Standard (Stable) channel. The release brings six key feature promotions, a revamped release process, and a new release train model to ensure consistent cadence and reliability. Below we answer common questions about this milestone release.
1. What is the Gateway API v1.5 release and when was it announced?
Gateway API v1.5 is the latest major version of the Kubernetes Gateway API, announced on February 27, 2026. It represents the project's biggest release yet, moving six experimental features to the Standard (stable) channel. The patch release v1.5.1 is already available. The release was coordinated by the Kubernetes SIG Network community, with special thanks to all contributors. Key features promoted include ListenerSet, TLSRoute, HTTPRoute CORS Filter, Client Certificate Validation, Certificate Selection for Gateway TLS Origination, and ReferenceGrant.
2. What major changes were introduced to the release process?
As of v1.5, the Gateway API project has adopted a release train model inspired by Kubernetes' own SIG Release workflow. Under this model, a feature freeze date is set, and any features ready by that date are included in the release. This applies equally to Experimental and Standard channel features, and also to documentation: if documentation isn't ready, the feature isn't shipped. The goal is to produce a more reliable and predictable release cadence. Alongside this change, the project introduced dedicated Release Manager and Release Shadow roles to oversee the process. Flynn (Buoyant) and Beka Modebadze (Google) coordinated the v1.5 release and will continue for the next cycle.
3. What is ListenerSet and why was it promoted to stable?
ListenerSet is a new resource that allows listeners to be defined independently and merged onto a target Gateway. Previously, all listeners had to be specified directly on the Gateway object, which created coordination challenges in complex or multi-tenant environments. Platform and application teams often needed to modify the same Gateway, making safe delegation of individual listeners difficult. ListenerSet solves this by enabling separate ownership of listeners, extending existing Gateways without modifying the original resource, and supporting more than 64 listeners per shared Gateway. This is critical for large-scale deployments with multiple hostnames. Even with ListenerSet, the listener field on the Gateway remains mandatory and must have at least one valid listener.
4. How does ListenerSet work and what problem does it solve?
A ListenerSet resource attaches to a Gateway and contributes one or more listeners. The Gateway controller is responsible for merging listeners from the Gateway resource itself and any attached ListenerSet resources. For example, a central infrastructure team might define a Gateway with a default HTTP listener, while two different application teams define their own ListenerSet resources in separate namespaces. Both ListenerSets attach to the same Gateway and contribute additional listeners. This solves the problem of safe delegation: application teams can manage their own listeners without needing direct access to the Gateway object. It also dramatically improves scalability by allowing hundreds of listeners on a single Gateway, fulfilling the needs of large-scale, multi-tenant Kubernetes deployments.
5. What other features were promoted to stable in this release?
Besides ListenerSet, five other features moved from Experimental to Standard in Gateway API v1.5:
- TLSRoute – enables routing of TLS traffic based on SNI, allowing secure, non-HTTP traffic management.
- HTTPRoute CORS Filter – adds built-in support for Cross-Origin Resource Sharing (CORS) headers directly in HTTPRoute rules, simplifying frontend integrations.
- Client Certificate Validation – allows Gateways to require and validate client certificates for mTLS connections.
- Certificate Selection for Gateway TLS Origination – enables fine-grained control over which certificate is used when the Gateway originates TLS connections to backends.
- ReferenceGrant – manages cross-namespace references between resources, enabling safe delegation of routes and backends across namespace boundaries.
6. How does the new release train model benefit the Gateway API project?
The release train model provides a structured, time-based cadence similar to Kubernetes core releases. By establishing a feature freeze date, the project ensures that only fully ready features are included, which improves reliability and predictability. Both Experimental and Standard features must meet the same documentation and testing requirements. This model reduces the risk of last-minute delays and allows contributors to plan their work around fixed milestones. It also facilitates better communication with the community about what to expect in each release. The introduction of Release Manager and Release Shadow roles further professionalizes the process, ensuring consistent oversight and continuous improvement.
7. What roles were added to manage the release process?
With the adoption of the release train model, Gateway API introduced two new roles: Release Manager and Release Shadow. The Release Manager is responsible for coordinating the entire release cycle, including setting the feature freeze date, tracking feature readiness, merging final changes, and publishing the release artifacts. The Release Shadow assists the manager and learns the process, ensuring continuity for future releases. For v1.5, Flynn (Buoyant) served as Release Manager and Beka Modebadze (Google) as Release Shadow. Both will continue in their roles for the next release, helping to refine the process and address any rough edges.