Gateway API v1.3.0
Release Notes
Changes since v1.3.0-rc.2
Changes since v1.2.1
Noteworthy Changes for Implementors
This section is intended to be a guide for API changes that might inspire or require implementation changes. None of these API changes represent breaking changes.
OverlappingTLSConfig for Connection Coalescing
A new OverlappingTLSConfig condition has been added to Gateway Listeners to indicate situations where
Connection Coalescing could be problematic. The Gateway specification for handling Hostname and SNI matching for HTTPS
requests has been clarified and now recommends that implementations return 421 HTTP code responses in certain cases.
- Implementation of GEP-3567 - TLS Updates for Connection Coalescing. (#3630,@robscott)
- Add GEP-3567: Gateway TLS Updates for HTTP/2 Connection Coalescing. (#3572,@robscott)
Move BackendTLSPolicy SubjectAltNames from Core to Extended
- The
SubjectAltNamesfield ofBackendTLSPolicychanged from Core to Extended feature. (#3591,@mlavacca)
The backendRef filter must send traffic to the correct backends when weighted routing is configured
- A new conformance test was added to ensure
backendReffilters don't affect weighted routing. (#3604,@dprotaso)
Clarify reasons for certain object status conditions
- Set proper reason for Gateway
parametersRefAcceptedcondition whenparametersRefis invalid. (#3579,@mlavacca) - Improve GatewayClass
GatewayClassReasonInvalidParametersreason description. (#3553,@mlavacca)
BackendTLSPolicy
GRPCRoute
Gateway.Spec.Addresses changes
A new type GatewaySpecAddress replaces GatewayAddress. In GatewayAddress the Value field was required. In
GatewaySpecAddress the Value field is optional. When the Value is unspecified, if an implementation supports that,
it SHOULD automatically assign an address. If an implementation does not support an empty Value, it MUST set the
Programmed condition in status to false with a reason of "AddressNotAssigned". The Addresses field in
Gateway.Spec has changed from type []GatewayAddress to []GatewaySpecAddress.
Standard Channel Additions and Changes
The Standard channel is Gateway API's set of maximally-stable install files. Only features with the best testing and support are added to the standard channel. This channel should be considered GA or stable, and future changes will be fully backwards compatible.
Percentage-Based Request Mirroring 🎉
This feature enhances the existing request mirroring feature
by allowing users to specify a percentage of requests to be mirrored in both HTTPRoute
and GRPCRoute objects.
This feature has graduated to Standard and is now considered GA or Stable.
This feature's name for conformance tests (and GatewayClass status reporting) is
HTTPRouteRequestPercentageMirror.
This feature's status is Extended, meaning that it is optional for
implementations to support. If you're using Experimental Channel, you can refer
to the supportedFeatures field in the status of any GatewayClass.
Relevant PRs:
- Promote percentage-based-request-mirroring GEP-3171 to standard (#3638,@LiorLieberman)
- Add conformance tests for percentage-based request mirroring (#3508,@LiorLieberman)
Experimental Channel Additions and Changes
The Experimental Channel is Gateway API's channel for testing out changes and gaining confidence with them before allowing them to go to Standard.
This channel may include features that are changed or removed later!
New experimental resources now start with "X"
This release introduces 2 new experimental resources:
- XBackendTrafficPolicy
- XListenerSet
Both of these resources are described in more detail below. As you may notice,
these resource names start with X and are part of an effort to distinguish
experimental channel resources from standard channel resources.
In addition to the separate names, these resources are also part of the
x-k8s.io API group instead of k8s.io, as a further effort to signal the
experimental nature of these resources.
In practice this means two things:
- These resources can coexist with standard channel resources
- Migrating to standard channel will require recreating these resources with the standard channel names and API Group (both lacking the "x" prefix)
For more context on this change, refer to the [related discussion](https://github.com/kubernetes-si
[truncated]