Kubernetes SIG Network has officially released Gateway API v1.5, the largest update yet, moving six popular experimental features to the Standard (GA) channel. The release, dated February 27, 2026, is immediately available, with a patch version 1.5.1 already out.
Key Features Promoted to Stable
The six features now stable include ListenerSet, TLSRoute, HTTPRoute CORS Filter, Client Certificate Validation, Certificate Selection for Gateway TLS Origination, and ReferenceGrant. These were among the most requested capabilities from the community.
ListenerSet: A Game Changer for Multi-Tenancy
ListenerSet addresses a long-standing pain point: coordinating listeners across platform and application teams. Previously, all listeners had to be defined on the Gateway object, leading to conflicts and complex delegation.
“ListenerSet allows listeners to be defined independently and merged onto a target Gateway, safely delegating ownership without modifying the original resource,” said Dave Protasowski, lead for the feature.
This also enables more than 64 listeners per Gateway, critical for large-scale deployments with multiple hostnames.
New Release Process: Train Model
Gateway API v1.5 introduces a release train model, where features are shipped on a fixed freeze date if ready. Documentation must also be complete for a feature to be included.
“This gives us a more reliable cadence, inspired by Kubernetes’ own release process,” said Flynn of Buoyant, a Release Manager for the project. Beka Modebadze (Google) also served as Release Shadow, both continuing for the next cycle.
Background: From Experimental to Stable
Gateway API has long maintained an Experimental channel for features under development. Promotion to Standard requires rigorous testing and community feedback. The v1.5 batch had been in Experimental for multiple releases, with extensive real-world use validating their stability.
What This Means
For platform engineers, the stabilization of ListenerSet and other features means reduced risk and improved scalability in production. Multi-tenant clusters can now delegate listener management safely without central bottlenecks. The new release process promises predictable updates, making Gateway API a more enterprise-ready ingress solution.
Users should update their Gateway controller implementations to support v1.5. The deprecated experimental versions will be phased out in future releases.