Gateway API v1.3.0 introduces enhancements like percentage-based request mirroring, CORS filtering, Gateway merging, and retry budgets.
The release includes percentage-based request mirroring allowing users to mirror a subset of requests, enabling testing without impacting all client responses.
New experimental features in this release include CORS filtering for cross-origin resource sharing and XListenerSets for merging Listeners.
XListenerSets allow shared listeners across Gateways and enable delegation of listener configuration, such as TLS, to applications in different namespaces.
Retry budgets (XBackendTrafficPolicy) in v1.3.0 allow configuring limits on client-side retries for a destination Service over a specified interval.
To try out these features, install the Experimental channel Gateway API YAMLs and follow the Getting Started Guide.
Conformant implementations to Gateway API v1.3 experimental features include Airlock Microgateway, Cilium, Envoy Gateway, and Istio.
Users running Kubernetes 1.26 or later can leverage Gateway API v1.3 without needing to upgrade Kubernetes itself.
The community is encouraged to get involved, explore use-cases, try existing Gateway controllers, and participate in shaping the future of Gateway API.
Gateway API v1.3.0 signifies progress in Kubernetes routing APIs and offers opportunities for community engagement and feature exploration.