News › networking
By Zayden R., August 4, 2026
Kubernetes has released Gateway API v1.6, elevating TCPRoute and UDPRoute to Standard, enabling stable L4 protocol routing. This update is crucial for engineers using raw TCP and UDP traffic in their Kubernetes setups.
Kubernetes has released Gateway API v1.6.0, marking a significant milestone with the graduation of TCPRoute and UDPRoute to Standard. This release, announced by the Kubernetes SIG Network community, brings stable layer 4 protocol routing to the forefront, a feature that engineers have long awaited. Previously, Gateway API provided a robust routing model for HTTP and TLS traffic, but left those needing raw protocol support over TCP or UDP to rely on less portable solutions.
With TCPRoute and UDPRoute now part of the v1 API version, users can route traffic to backends based solely on protocol and port, without any layer 7 processing. This change is particularly beneficial for workloads such as databases, DNS, and IoT telemetry, which rely on raw TCP and UDP traffic. The previous v1alpha2 versions of these routes have been deprecated, with plans for removal in future releases.
From a practical standpoint, integrating these routes into a Gateway involves creating a listener that allows TCPRoute attachment. For example, a Gateway can be defined with a listener using TCP on port 12345, allowing TCPRoute to attach and forward traffic to a backend service. This capability enhances the flexibility and portability of Kubernetes-based network configurations.
Additionally, the release introduces an experimental API group separation, clearly delineating between stable and experimental resources. This clarity in API boundaries is set to foster innovation while maintaining the robustness of core functionalities. For engineers, these updates mean a more versatile and reliable networking capability within Kubernetes, aligning with modern service networking needs.
The Linux Camp teaches these topics as hands-on labs on real virtual machines, verified as you type.