Update module sigs.k8s.io/gateway-api to v1.3.0 #3335
+62
−58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.2.1
->v1.3.0
Release Notes
kubernetes-sigs/gateway-api (sigs.k8s.io/gateway-api)
v1.3.0
Compare Source
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 whereConnection 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.
Move
BackendTLSPolicy
SubjectAltNames
from Core to ExtendedSubjectAltNames
field ofBackendTLSPolicy
changed from Core to Extended feature. (#3591,@mlavacca)The
backendRef
filter must send traffic to the correct backends when weighted routing is configuredbackendRef
filters don't affect weighted routing. (#3604,@dprotaso)Clarify reasons for certain object status conditions
parametersRef
Accepted
condition whenparametersRef
is invalid. (#3579,@mlavacca)GatewayClassReasonInvalidParameters
reason description. (#3553,@mlavacca)BackendTLSPolicy
BackendTLSPolicy
. (#3496,@snorwin)GRPCRoute
GRPCRoute
match limit from 8 -> 64 (#3601,@EyalPazz)Gateway.Spec.Addresses changes
A new type
GatewaySpecAddress
replacesGatewayAddress
. InGatewayAddress
theValue
field was required. InGatewaySpecAddress
theValue
field is optional. When theValue
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". TheAddresses
field inGateway.Spec
has changed from type[]GatewayAddress
to[]GatewaySpecAddress
.value
field inGateway.Spec.Addresses
array optional (#3616,@EyalPazz)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 thestatus
of any GatewayClass.Relevant PRs:
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:
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 distinguishexperimental 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 ofk8s.io
, as a further effort to signal theexperimental nature of these resources.
In practice this means two things:
the standard channel names and API Group (both lacking the "x" prefix)
For more context on this change, refer to the related discussion.
CORS (Cross Origin Resource Sharing) Filter
GEP-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)XListenerSets (Standard Mechanism to Merge Gateways)
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 toXListenerSet
.The object group name has changed from
gateway.networking.k8s.io
togateway.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 toXListenerSet
. The ResourceBackendTrafficPolicy
has been renamed toXBackendTrafficPolicy
. (#3682,@mlavacca)XBackendTrafficPolicy (Retry Budgets)
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, thus
BackendTrafficPolicy
has changed toXBackendTrafficPolicy
. The object group name has changed fromgateway.networking.k8s.io
togateway.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 toXListenerSet
. The ResourceBackendTrafficPolicy
has been renamed toXBackendTrafficPolicy
. (#3682,@mlavacca)budgetPercent
andbudgetInterval
tobudget.percent
and
budget.interval
respectively. (#3695,@youngnick)BackendLBPolicy has been replaced by XBackendTrafficPolicy
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).
GEPs
Documentation
InvalidParameters
reason SHOULD be used with theAccepted
condition in case the object referenced does not exist, is of an unsupported kind, or is malformed. (#3579,@mlavacca)sessionPersistence.cookieConfig.lifetimeType
(#3540,@arkodg)(#3657,@blake),
(#3400,@jsoref),
(#3626,@zirain),
(#3565,@Vaniog),
(#3485,@fatsheep9146)
LocalObjectReference
(empty string infers core API group) (#3597,@EyalPazz)Cleanup
Bug or Regression
HTTPCORSFilter.AllowMethods
(#3667,@EyalPazz)
Dependencies
Added
Changed
fe59bbe
→8a7402a
04be3eb
→104605a
b8732ec
→ef43131
ddb44da
→5f5ef82
ddb44da
→1a7da9e
51d4e06
→2b36238
k8s.io/kube-openapi:
8948a66
→32ad38e
18e509b
→3ea5e8c
bc3834c
→9aa6b5e
Removed
9cce18d
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.