The short answer
Gateway API v1.5 (February 2026) promoted six features to the Standard channel, including ListenerSet and TLSRoute. v1.6 (June 2026) graduated TCPRoute and UDPRoute to Standard in the v1 API and moved experimental resources to a separate API group. Teams on Experimental TLSRoutes must plan the move, because v1.5 Standard does not include their stored versions.
Need someone who has run this upgrade?
Conntal places Kubernetes engineers on contract, contract-to-hire or direct hire, each screened by a practitioner before you see a CV.
With Ingress NGINX retired, Gateway API is where most Kubernetes ingress work is heading. Two releases in 2026 changed what is stable enough to build on.
v1.5: six features to Standard
Released on 27 February 2026, v1.5 concentrated on promoting Experimental features to the Standard channel, Gateway API's GA channel [1]. The six promotions were ListenerSet, TLSRoute, the HTTPRoute CORS filter, client certificate validation, certificate selection for Gateway TLS origination, and ReferenceGrant [1]. The project also moved to a release-train model, shipping whatever is ready at feature freeze [1].
ListenerSet matters most for platform teams: listeners can be defined independently — for example by application teams in their own namespaces — and merged onto a shared Gateway, which also lifts the limit of 64 listeners on a single Gateway [1].
v1.6: TCP and UDP become Standard
- Released on 30 June 2026, v1.6 graduated TCPRoute and UDPRoute to Standard in the v1 API, giving raw-protocol workloads — databases, DNS, VoIP, IoT telemetry — a portable way onto a Gateway [2].
- The v1alpha2 versions of both are deprecated and will be removed in a future release [2].
- Experimental resources moved to a separate API group, gateway.networking.x-k8s.io, with an X prefix, to make the line between experimental and standard explicit [2].
- A new experimental XBackend resource adds a Gateway API-native backend, including opt-in external hostnames for egress [2].
What we ask
We ask platform engineers how they would upgrade Gateway API CRDs on a shared cluster where some teams adopted Experimental routes early. The strong answer starts with an inventory of stored versions and a per-tenant plan; the weak one runs kubectl apply on the new manifests.
Need someone who has run this upgrade?
Conntal places Kubernetes engineers on contract, contract-to-hire or direct hire, each screened by a practitioner before you see a CV.
Sources
- [1] Kubernetes Blog (SIG Network), Gateway API v1.5: Moving features to Stable. 21 April 2026.Primary source
- [2] Kubernetes Blog (SIG Network), Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard. 3 August 2026.Primary source
Go deeper with the engineers who run it
Conntal is the staffing arm of AceMQ. When you need the platform supported rather than a person placed, these are the pages to read.
Related questions
Which Gateway API features are Standard as of 2026?
v1.5 promoted ListenerSet, TLSRoute, the HTTPRoute CORS filter, client certificate validation, certificate selection for Gateway TLS origination and ReferenceGrant to Standard. v1.6 added TCPRoute and UDPRoute in the v1 API.
Will upgrading to Gateway API v1.5 break my TLSRoutes?
Existing Experimental TLSRoutes stored in v1alpha2 or v1alpha3 become unusable if you install v1.5 Standard over an earlier Experimental install, because those versions are not in the v1.5 Standard manifests.