Gateway API v1.2: WebSockets, Timeouts, Retries, and More

Gateway API v1.2: WebSockets, Timeouts, Retries, and More Breaking changes GRPCRoute and ReferenceGrant v1alpha2 removal Change to. status. supportedFeatures (experimental) Graduations to the standard channel HTTPRoute timeouts Gateway infrastructure labels and annotations Backend protocol support New additions to experimental channel Named rules for *Route resources HTTPRoute retry support HTTPRoute percentage-based mirroring Additional backend TLS configuration More changes Project updates Release process improvements gwctl moves out Maintainer changes Try it out Get involved Related Kubernetes blog articles Kubernetes SIG Network is delighted to announce the general availability of Gateway API v1.2! This version of the API was released on October 3, and we're delighted to report that we now have a number of conformant implementations of it for you to try out. Gateway API v1.2 brings a number of new features to the Standard channel (Gateway API's GA release channel), introduces some new experimental features, and inaugurates our new release process — but it also brings two breaking changes that you'll want to be careful of. v1alpha2 Now that the v1 versions of GRPCRoute and ReferenceGrant have graduated to Standard, the old v1alpha2 versions have been removed from both the Standard and Experimental channels, in order to ease the maintenance burden that perpetually supporting the old versions would place on the Gateway API community. v1 v1alpha2 Before upgrading to Gateway API v1.2, you'll want to confirm that any implementations of Gateway API have been upgraded to support the v1 API version of these resources instead of the v1alpha2 API version. Note that even if you've been using v1 in your YAML manifests, a controller may still be using v1alpha2 which would cause it to fail during this upgrade. Additionally, Kubernetes itself goes to some effort to stop you from removing a CRD version that it thinks you're using: check out the release notes for more information about what you need to do to safely upgrade. status. supportedFeatures A much smaller breaking change:. status. supportedFeatures in a Gateway is now a list of objects instead of a list of strings.