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.
Table of contents
TCPRoute and UDPRoute graduate to StandardXBackend arrives in ExperimentalExperimental resources move off the standard API groupWhat's next & getting involved4.7K Impressions1 Comment