# Gateway API v1.5: Moving features to Stable

DevFeed: [Gateway API v1.5: Moving features to Stable](<https://devfeed.tech/articles/gateway-api-v1-5-moving-features-to-stable-4535.md>)

Original publisher: [Read original article](<https://kubernetes.io/blog/2026/04/21/gateway-api-v1-5/>)

Published: 2026-04-21T16:30:00Z

Content type: release

Language: en

Sources: [Kubernetes Blog](<https://devfeed.tech/sources/kubernetes-blog.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [Network](<https://devfeed.tech/topics/network.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [network](<https://devfeed.tech/tags/network.md>), [release](<https://devfeed.tech/tags/release.md>), [release-cadence](<https://devfeed.tech/tags/release-cadence.md>), [scalability](<https://devfeed.tech/tags/scalability.md>), [tls](<https://devfeed.tech/tags/tls.md>)

## AI overview

Gateway API v1.5 promotes six features from Experimental to Standard, including ListenerSet, TLSRoute, HTTPRoute, CORS Filter, client certificate validation, certificate selection for Gateway TLS origination, and ReferenceGrant. The release also introduces a release-train process intended to improve cadence and documentation readiness.

## Source excerpt

The Kubernetes SIG Network community presents the release of Gateway API (v1.5)! Released on February 27, 2026, version 1.5 is our biggest release yet, and concentrates on moving existing Experimental features to Standard (Stable). The Gateway API v1.5.1 patch release is already available. The Gateway API v1.5 brings six widely-requested feature promotions to the Standard channel (Gateway API's GA release channel): ListenerSet TLSRoute HTTPRoute CORS Filter Client Certificate Validation Certificate Selection for Gateway TLS Origination ReferenceGrant Special thanks for Gateway API Contributors for their efforts on this release. New release process As of Gateway API v1.5, the project has moved to a release train model, where on a feature freeze date, any features that are ready are shipped in the release. This applies to both Experimental and Standard, and also applies to documentation -- if the documentation isn't ready to ship, the feature isn't ready to ship. We are aiming for this to produce a more reliable release cadence (since we are basing our work off the excellent work done by SIG Release on Kubernetes itself). As part of this change, we've also introduced Release Manager and Release Shadow roles to our release team. Many thanks to Flynn (Buoyant) and Beka Modebadze (Google) for all the great work coordinating and filing the rough edges of our release process. They are both going to continue in this role for the next release as well. New standard featuresListenerSet Leads: Dave Protasowski, David Jumani GEP-1713 Why ListenerSet? Prior to ListenerSet, all listeners had to be specified directly on the Gateway object. While this worked well for simple use cases, it created challenges for more complex or multi-tenant environments: Platform teams and application teams often needed to coordinate changes to the same Gateway Safely delegating ownership of individual listeners was difficult Extending existing Gateways required direct modification of the original res