Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard

Kubernetes Gateway API just reached a significant milestone with version 1.6.0, moving TCP and UDP routing capabilities from experimental to standard status. If you’ve been working with Kubernetes ingress controllers, you’ve probably felt the friction of managing different tools for HTTP traffic versus everything else. Gateway API aims to solve this fragmentation by providing a unified, role-based approach to handling all types of network traffic—and this release signals that the community is confident enough in TCP/UDP support to make it stable.

For those new to Gateway API, think of it as the modern successor to the traditional Ingress resource. Where Ingress was designed primarily for HTTP/HTTPS traffic with a pretty limited API surface, Gateway API separates concerns between infrastructure operators (who manage gateways) and application developers (who define routes). TCPRoute and UDPRoute extend this model beyond HTTP, letting you define how traffic flows for databases, game servers, IoT devices, and any other protocol that doesn’t speak HTTP. Technically, this means you can now attach routes to a gateway listener configured for TCP or UDP ports, and the control plane handles the rest—no more juggling multiple tools or custom controllers for non-HTTP protocols.

Why does this matter practically? Many cloud-native applications need more than HTTP. If you’re running a PostgreSQL connection pool, a DNS service, a gaming backend, or real-time data streaming, you’ve had to either use separate ingress solutions or expose services directly. With TCPRoute and UDPRoute now stable, platform teams can offer a single, consistent interface for all network traffic. This reduces operational overhead, makes networking policies easier to audit, and gives developers a familiar pattern across protocol types. You can now define authentication, rate limiting policies, and load balancing rules in the same declarative way for TCP traffic as you do for HTTP.

The graduation to standard status also has implications for tooling maturity. Gateway API implementations like Cilium, Contour, and others can now confidently build TCP/UDP support knowing the API won’t change unexpectedly. If you’re planning network infrastructure for a multi-tenant platform or designing how microservices communicate, this is worth evaluating. The unified model reduces cognitive load for your teams and positions you well for infrastructure-as-code practices that scale beyond HTTP-only workloads.