Gateway API v1.6: TCP and UDP Routing Are Finally Production-Ready
Enterprise Developer PlatformsKubernetes Gateway API v1.6 just moved TCPRoute and UDPRoute out of the experimental bucket, which means any platform team routing non-HTTP traffic — databases, DNS, VoIP, gaming, IoT telemetry — no longer has to choose between vendor lock-in and unsupported APIs.
What Happened
TCPRoute and UDPRoute are Layer 4 routing resources: they direct traffic to backends based purely on protocol and port, with no application-layer awareness. Before v1.6, both lived in the Experimental channel at the v1alpha2 API version, meaning they carried no stability guarantee and could break between releases. In v1.6, both graduate to the Standard channel at v1, putting them under Kubernetes’ full API stability guarantees. The v1alpha2 versions are now deprecated and will be removed in a future release. The release also separates all remaining experimental resources into their own API group (gateway.networking.x-k8s.io, with resources prefixed X), drawing a hard line between what’s safe for production and what’s still in flux.
Why It Matters
Before this graduation, teams needing production-grade TCP or UDP routing had two options: fall back to plain Kubernetes Services (losing Gateway API’s richer routing model) or adopt an implementation-specific CRD (locking into one Gateway controller vendor). Standard-channel TCPRoute and UDPRoute close that gap — the same portable routing model that made Gateway API compelling for HTTP now extends to raw TCP and UDP, backed by the same stability contract.
What This Means for Builders
If you’ve been running L4 traffic through Services or a vendor-specific extension because TCPRoute/UDPRoute weren’t stable enough to commit to, that constraint is gone. Migrating database, DNS, or telemetry routing onto Standard-channel Gateway API resources removes a dependency on a single Gateway controller implementation without sacrificing production support. Budget time to move off v1alpha2 before it’s removed — deprecated doesn’t mean urgent, but it does mean scheduled.
The Pattern
Gateway API’s steady march toward covering every protocol type continues a theme Stack Archive has tracked through the ingress-nginx retirement — Kubernetes networking is consolidating around Gateway API as the single standard, not just for HTTP.
The So What
If TCP or UDP routing on Kubernetes has been running on a workaround, v1.6 is the release that removes the excuse. Plan the migration off v1alpha2 now, while it’s still deprecated rather than deleted.
Source: Kubernetes Blog
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →