Gateway API v1.0.0
Release Notes
On behalf of Kubernetes SIG Network, we are pleased to announce the v1.0 release! This release marks a huge milestone for this project. Several key APIs are graduating to GA (generally available), while other significant features have been added to the Experimental channel.
It's been four years since this project began, and we would never have gotten here without the support of a dedicated and active community. The maintainers would like to thanks everyone who's contributed to Gateway API, whether in the form of commits to the repo, discussion, ideas, or general support. We literally couldn't have gotten this far without you.
This project is nowhere near finished, as you can see from the large amount of features being added into the Experimental Channel. With such a big set of things still to do, contributors and contributions are more vital than ever. Please feel welcome to join our community!!
Gateway, GatewayClass, and HTTPRoute are GA 🎉
Gateway, GatewayClass, and HTTPRoute have all graduated to GA with a v1 API
version. Although these APIs will continue to grow with future additions, the
versions of these resources available via the Standard Channel are stable and
recommended for use in production. Many implementations are fully passing
conformance tests that cover the functionality of each of these resources. These
APIs are graduating to GA with only minor spec clarifications since the v0.8.0
release.
CEL Migration
Starting in v0.8.0, Gateway API CRDs now include CEL validation. In this release
the validating webhook is no longer bundled with CRD installation. Instead we
include a separate webhook-install.yaml file as part of the release artifacts.
If you're running Kubernetes 1.25+, we do not recommend installing the webhook and additionally suggest that you uninstall any previously installed versions of the webhook.
If you're still running Kubernetes 1.23 or 1.24, we recommend installing the webhook until you can upgrade to Kubernetes 1.25 or newer.
New Experimental Features
There are several exciting new experimental features in this release:
BackendTLSPolicy
A new BackendTLSPolicy resource has been introduced for configuring TLS
connections from Gateways to Backends. This allows you to configure the Gateway
to validate the certificates served by Backends. For more information, refer to
GEP 1897.
Primary Author: @candita
HTTPRoute Timeouts
HTTPRoute has a new Timeouts field on Route Rules. This allows you to
configure overall Request Timeouts as well as Backend Request Timeouts. For more
information, refer to GEP 1742.
Primary Authors: @frankbu, @SRodi
Gateway Infrastructure Labels
Gateway has a new Infrastructure field that allows you to specify Labels or
Annotations that you'd like to be propagated to each resource generated for a
Gateway. For example, these labels and annotations may be copied to Services and
Deployments provisioned for in-cluster Gateways, or to other
implementation-specific resources, such as Cloud Load Balancers. For more
information, refer to GEP 1762.
Primary Author: @howardjohn
WebSockets, HTTP/2, and More
Some coordinated work across both Gateway API and upstream Kubernetes has defined 3 new values for the AppProtocol field on Service Ports:
kubernetes.io/h2c- HTTP/2 over cleartext as described in RFC7540kubernetes.io/ws- WebSocket over cleartext as described in RFC6445kubernetes.io/wss- WebSocket over TLS as described in RFC6455
These can now be used with Gateway API to describe the protocol to use for connections to Kubernetes Services. For more information, refer to GEP 1911.
A new CLI tool: gwctl
An experimental new CLI tool and kubectl plugin, gwctl aims to improve the UX when interacting with Gateway API. Initially it is focused on Policy Attachment, making it easier to understand which policies are available in a cluster, and which have been applied. In future releases, we hope to expand the scope of this tool to provide more detailed responses when getting and describing Gateway API resources. Note that this tool is still in very early stages and it's very likely that future releases will include breaking changes for gwctl. For more information, refer to the gwctl Readme.
Primary Author: @gauravkghildiyal
Everything Else
Of course there's a lot more in this release:
Spec Clarifications
- Clarify that the Gateway Listener status AttachedRoutes field is a count of the number of Routes associated with a Listener regardless of Gateway or Route status. (#2396, @sunjayBhatia)
- Gateway: A new concept called "Listener Isolation" has been introduced to describe the recommendation that at most one Listener matches a request, and only Routes attached to that Listener are used for routing. (#2465, @robscott)
- Experimental Channel: For ParentRefs to be considered distinct, they either both need to specify a distinct SectionName, both need to specify a distinct Port, or both. (#2433, @robscott)
- Updated rules about Listener uniqueness to use the term
distinct(#2436, @youngnick)
Status
- GatewayClass Status: A new experimental
supportedFeaturesfield has been added. Implementations should populate this with the features they support. (#2461, @Liorlieberman, @robscott) - GatewayClass Status: A new SupportedVersion condition has been added that MUST be set when a GatewayClass is accepte
[truncated]