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.
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.
BackendTLSPolicy
SubjectAltNames
from Core to Extended
SubjectAltNames
field of BackendTLSPolicy
changed from Core to Extended feature. (#3591,@mlavacca)backendRef
filter must send traffic to the correct backends when weighted routing is configured
backendRef
filters don't affect weighted routing. (#3604,@dprotaso)parametersRef
Accepted
condition when parametersRef
is invalid. (#3579,@mlavacca)GatewayClassReasonInvalidParameters
reason description. (#3553,@mlavacca)A new type GatewaySpecAddress
replaces GatewayAddress
. In GatewayAddress
the Value
field was required. InGatewaySpecAddress
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 theProgrammed
condition in status to false with a reason of "AddressNotAssigned". The Addresses
field inGateway.Spec
has changed from type []GatewayAddress
to []GatewaySpecAddress
.
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.
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) isHTTPRouteRequestPercentageMirror
.
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:
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:
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 thex-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:
For more context on this change, refer to the related discussion.
CORS (Cross Origin Resource Sharing) FilterGEP-1767 describes how to add
configuration of CORS filters on HTTPRoute objects, and in this release, this change
has moved to Experimental.
Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
HTTPRoute
(#3637,@robscott)HTTPRouteFilter.CORS.AllowCredentials
to expect a boolean and not a string (#3656,@EyalPazz)HTTPRouteFilterType
(#3668,@EyalPazz)GEP-1713 defines a new mechanism to merge listeners into a single
Gateway, and in this release, this change has moved to Experimental. Following a new naming convention, an
experimental object name is prefaced with an X, thus ListenerSet
has changed to XListenerSet
.
The object group name has changed from gateway.networking.k8s.io
to gateway.networking.x-k8s.io
.
Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
ListenerSet
s across namespaces (#3632,@dprotaso)ListenerSet
API & Generate Clients (in the group gateway.networking.k8s-x.io) (#3588,@dprotaso)ListenerSet
has been renamed to XListenerSet
. The Resource BackendTrafficPolicy
has been renamed toXBackendTrafficPolicy
. (#3682,@mlavacca)GEP-3388
specifies the configuration of a "retry budget" across all endpoints of a destination service in order to prevent
additional client-side retries after reaching a configured threshold. The budget can be configured using a maximum
percentage of active requests, or an interval during which requests will be considered. In this release, this change has
moved to Experimental. Following a new naming convention, an experimental object name is prefaced with an X, thusBackendTrafficPolicy
has changed to XBackendTrafficPolicy
. The object group name has changed fromgateway.networking.k8s.io
to gateway.networking.x-k8s.io
.
Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
BackendTrafficPolicy
with ability to configure budgeted retries (#3607,@ericdbishop)ListenerSet
has been renamed to XListenerSet
. The Resource BackendTrafficPolicy
has been renamed toXBackendTrafficPolicy
. (#3682,@mlavacca)budgetPercent
and budgetInterval
to budget.percent
budget.interval
respectively. (#3695,@youngnick)In the interest of combining similar concepts in a single policy, we've decided
to merge the contents of BackendLBPolicy (session persistence) into
XBackendTrafficPolicy (retry budgets).
InvalidParameters
reason SHOULD be used with the Accepted
condition in case the object referenced does not exist, is of an unsupported kind, or is malformed. (#3579,@mlavacca)sessionPersistence.cookieConfig.lifetimeType
(#3540,@arkodg)LocalObjectReference
(empty string infers core API group) (#3597,@EyalPazz)HTTPCORSFilter.AllowMethods
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4