--- title: Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard description: Kubernetes Gateway API v1.6.0 has been released, bringing two major changes. TCPRoute and UDPRoute have graduated from Experimental to Standard (v1 API),... canonical: https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard | daily.dev og:description: Kubernetes Gateway API v1.6.0 has been released, bringing two major changes. TCPRoute and UDPRoute have graduated from Experimental to Standard (v1 API),... og:url: https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho og:image: https://api.daily.dev/og/posts/KmM6Ni7hO.png og:image:alt: Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard **[Kubernetes](https://daily.dev/sources/k8s)** · 6 min read · 10 upvotes · 1 comments ## Summary Kubernetes Gateway API v1.6.0 has been released, bringing two major changes. TCPRoute and UDPRoute have graduated from Experimental to Standard (v1 API), enabling portable layer 4 routing for workloads like databases, DNS, VoIP, and gaming without relying on implementation-specific CRDs. The release also introduces a new experimental API group separation: new experimental resources now live under gateway.networking.x-k8s.io with an X prefix (e.g., XBackend, XMesh), making the experimental vs. stable boundary explicit at the API group level rather than relying on version strings. XBackend, a new experimental resource, adds support for ExternalHostname destinations useful for egress use cases such as routing to external AI APIs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What changed for TCPRoute and UDPRoute in Gateway API 1.6.0? TCPRoute and UDPRoute graduated from the Experimental channel to Standard and moved to the v1 API version in Gateway API 1.6.0, released June 30. The older v1alpha2 versions of both resources are now deprecated and will be removed in a future release, so manifests should migrate to gateway.networking.k8s.io/v1. _Track Gateway API version migrations like this one by following Kubernetes networking updates on daily.dev._ ### How do I route raw TCP traffic through a Kubernetes Gateway using TCPRoute? Define a Gateway listener with protocol TCP and a port, allowing TCPRoute kind attachment, then create a TCPRoute with parentRefs pointing to that listener's sectionName and backendRefs naming the target Service and port. Traffic arriving on the Gateway's port is proxied to the backend Service's endpoints; omitting sectionName and port attaches the route to every TCP listener. _Developers wiring up layer 4 routing can find Gateway API configuration patterns like this via daily.dev._ ### What is the XBackend resource in Gateway API and what does it support? XBackend is a new experimental general-purpose decorator resource for Service and other backend types, introduced in Gateway API 1.6.0 in the gateway.networking.x-k8s.io/v1alpha1 group. Its first version supports ExternalHostname destinations for egress use cases such as calling external cloud APIs, a case Service cannot handle safely due to confused deputy attack risks; it is experimental and not production-ready. _Anyone evaluating egress routing options for cluster workloads can track XBackend's evolution on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@pdfopsdev** · 0 upvotes > the v1alpha2 to v1 bump is going to bite people who deployed TCPRoute assuming experimental meant stable enough to leave alone. worth checking your gateway controller's v1 support now, cilium and envoy gateway aren't always on the same graduation schedule. ## Similar posts on daily.dev - [The Gateway API shift: how Kubernetes networking actually works at scale](https://daily.dev/posts/the-gateway-api-shift-how-kubernetes-networking-actually-works-at-scale-t04kkbq5r) · Giant Swarm · 16 upvotes · 1 comments - [Kubernetes Ingress vs Gateway API](https://daily.dev/posts/kubernetes-ingress-vs-gateway-api-jwa9l6ig9) · Isovalent · 11 upvotes · 1 comments - [How to Move to the Gateway API: post ingress-nginx Retirement](https://daily.dev/posts/how-to-move-to-the-gateway-api-post-ingress-nginx-retirement-q3cqencll) · Pulumi · 5 upvotes · 0 comments - [AWS Load Balancer Controller Reaches GA with Kubernetes Gateway API Support](https://daily.dev/posts/aws-load-balancer-controller-reaches-ga-with-kubernetes-gateway-api-support-elzeyfvna) · InfoQ · 0 upvotes · 0 comments - [Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more](https://daily.dev/posts/cilium-1-20-gateway-api-externalauth-tcproute-udproute-eni-ipam-for-ipv6-and-more-yswg7phsz) · CNCF · 8 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#networking](https://daily.dev/tags/networking), [#gateway-api](https://daily.dev/tags/gateway-api) [View this post on daily.dev](https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard","url":"https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho"},"datePublished":"2026-08-03T17:57:55.806Z","dateModified":"2026-09-14T06:54:00.370Z","description":"Kubernetes Gateway API v1.6.0 has been released, bringing two major changes. TCPRoute and UDPRoute have graduated from Experimental to Standard (v1 API),...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Kubernetes","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Kubernetes","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/k8s","url":"https://daily.dev/sources/k8s"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"kubernetes,networking,gateway-api","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Kubernetes","item":"https://daily.dev/sources/k8s"},{"@type":"ListItem","position":3,"name":"Gateway API v1.6: TCPRoute and UDPRoute Graduate to Standard"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho","comment":[{"@type":"Comment","text":"the v1alpha2 to v1 bump is going to bite people who deployed TCPRoute assuming experimental meant stable enough to leave alone. worth checking your gateway controller’s v1 support now, cilium and envoy gateway aren’t always on the same graduation schedule.","datePublished":"2026-08-05T18:05:42.170Z","url":"https://daily.dev/posts/KmM6Ni7hO#c-IvOUCTDJJ","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/gateway-api-v1-6-tcproute-and-udproute-graduate-to-standard-kmm6ni7ho#faq","mainEntity":[{"@type":"Question","name":"What changed for TCPRoute and UDPRoute in Gateway API 1.6.0?","acceptedAnswer":{"@type":"Answer","text":"TCPRoute and UDPRoute graduated from the Experimental channel to Standard and moved to the v1 API version in Gateway API 1.6.0, released June 30. The older v1alpha2 versions of both resources are now deprecated and will be removed in a future release, so manifests should migrate to gateway.networking.k8s.io/v1. Track Gateway API version migrations like this one by following Kubernetes networking updates on daily.dev."}},{"@type":"Question","name":"How do I route raw TCP traffic through a Kubernetes Gateway using TCPRoute?","acceptedAnswer":{"@type":"Answer","text":"Define a Gateway listener with protocol TCP and a port, allowing TCPRoute kind attachment, then create a TCPRoute with parentRefs pointing to that listener's sectionName and backendRefs naming the target Service and port. Traffic arriving on the Gateway's port is proxied to the backend Service's endpoints; omitting sectionName and port attaches the route to every TCP listener. Developers wiring up layer 4 routing can find Gateway API configuration patterns like this via daily.dev."}},{"@type":"Question","name":"What is the XBackend resource in Gateway API and what does it support?","acceptedAnswer":{"@type":"Answer","text":"XBackend is a new experimental general-purpose decorator resource for Service and other backend types, introduced in Gateway API 1.6.0 in the gateway.networking.x-k8s.io/v1alpha1 group. Its first version supports ExternalHostname destinations for egress use cases such as calling external cloud APIs, a case Service cannot handle safely due to confused deputy attack risks; it is experimental and not production-ready. Anyone evaluating egress routing options for cluster workloads can track XBackend's evolution on daily.dev."}}]} ```