feat(deps): update gateway-api-crd ( v1.2.1 → v1.5.0 )#5521
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
feat(deps): update gateway-api-crd ( v1.2.1 → v1.5.0 )#5521renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports
|
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cluster-0-gateway-api-crd-1.x
branch
from
38d4043 to
caf0275
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/cluster-0-gateway-api-crd-1.x
branch
from
caf0275 to
748a6f0
Compare
| datasource | package | from | to | | ----------- | --------------------------- | ------ | ------ | | github-tags | kubernetes-sigs/gateway-api | v1.2.1 | v1.5.0 |
renovate
bot
force-pushed
the
renovate/cluster-0-gateway-api-crd-1.x
branch
from
748a6f0 to
b905909
Compare
renovate
bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.5.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
kubernetes-sigs/gateway-api (gateway-api-crd)
v1.5.0Compare Source
Warning: The Experimental channel CRDs are too large for a standard
kubectl apply. To work around this please usekubectl apply --server-side=trueinstead -- or, even better, usekubercto make server-side apply the default.Gateway API v1.5.0
Major Changes Since v1.4.1
Breaking Changes
TLSRoute
v1alpha2and XListenerSetSince TLSRoute and ListenerSet have graduated to the Standard channel, TLSRoute
v1alpha2and XListenerSet are no longer included in the Experimental channel.Additionally, note that TLSRoute's CEL validation requires Kubernetes 1.31 or higher.
Upgrades and ValidatingAdmissionPolicy
Gateway API 1.5 introduces a validating admission policy (VAP) called
safe-upgrades.gateway.networking.k8s.ioto guard against two specific concerns:These actions can't be known to be safe without detailed knowledge about your application and users. If you need to perform them, delete the
safe-upgrades.gateway.networking.k8s.ioVAP first.New Features
In this release, the following major features are moving to the
Standardchannel and are now considered generally available:v1(GEP-2643)Additionally, the ReferenceGrant resource is moving to
v1.Experimental
Full Changelog
Full Changelog: kubernetes-sigs/gateway-api@v1.4.1...v1.5.0
Dependencies
Added
Changed
1a19826→bd525da8d1bb00→ab9386aef028d9→ab9386ac297c0c→ec3ebc5d7b6acb→589584f0af2bda→914a6e7Removed
5ec99f8v1.4.1Compare Source
Warning: Regarding the Experimental CRDs - please note that the experimental CRDs for this release are too large for a standard
kubectl apply. You may receive an error likemetadata.annotations: Too long: may not be more than 262144 bytes. To work around this please usekubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml. We're looking into ways to reduce the size for future releases to avoid this.Note: The installation YAML originally published with this release on 2025-12-04 mistakenly included changes from PR 3823 in the Standard channel, and from PRs 3774, 3823, and 4158 in the Experimental channel. After discussion among the Gateway API maintainers, we decided that the changes were minor enough that it was safe to modify the YAML in-place, which we did on 2026-02-10. Apologies for the confusion!
Changes Since v1.4.0
BackendTLSPolicy
targetRefper policy while Gateway API works through edge cases around representing the status of multipletargetRefsin a single policy. This restriction is expected to be lifted in a future release. (#4316, #4298)statusis correctly marked as a subresource. (#4245)Conformance
Thanks to
Ciara Stacke, Lior Lieberman, Nick Young, Norwin Schnyder, Ricardo Pchevuzinske Katz, and zirain
Full Changelog
Full Changelog: kubernetes-sigs/gateway-api@v1.4.0...v1.4.1
v1.4.0Compare Source
Warning: Regarding the Experimental CRDs - please note that the experimental CRDs for this release are too large for a standard
kubectl apply. You may receive an error likemetadata.annotations: Too long: may not be more than 262144 bytes. To work around this please usekubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml. We're looking into ways to reduce the size for future releases to avoid this.Major Changes since v1.3.0
Breaking Changes
Experimental CORS Support in HTTPRoute - Breaking Change for AllowCredentials Field
Users of the
ExperimentalCORSAllowCredentialsfield can now specify false.The underlying API specification type has changed from a enum of type boolean to
just a boolean, so users deploying
HTTPRoutesvia libraries and evaluating theexperimental CORS support will need to adjust for the change in types. Please
see #3895 for more details.
Standard GRPCRoute - Spec Field Required (Technicality)
This PR makes
grpcroute.speca required field. This is technically abackward-incompatible change, as previously the field was unintentionally
treated as optional because we erroneously used
omitemptyon.spec(unlikeother APIs). Since the codebase didn't yet enforce explicit required markers,
that
omitemptyallowed a missing.spec.Because
.speccontains essential route configuration, omitting it renders aGRPCRouteunusable and causes route implementation to fail, so we expect thischange will not have adverse effects, but wanted to call it out all the same.
Please see #3937 for more details.
GEPs
New Features
In this release, the following major features are moving to the
Standardchannel and are now considered generally available:
In this release, we introduced the following new features are moving to the
Experimentalchannel, for implementations to evaluate:Gatewaysto program some routes by default.HTTPRoute.Other Iterations
Bug or Regression
Administrative
Changes by Kind
API
HTTPRoute
In the
Standardchannel, we've now added aNamefield toHTTPRouteRuleand
HTTPRouteMatch.Documentation
CI & Testing
Conformance Tests
Cleanup
Release Candidate Fixes
These are patches during the
v1.4.0release candidate cycles from issues found or other small improvements needed for the final release:New Contributors
Full Changelog: kubernetes-sigs/gateway-api@v1.3.0...v1.4.0
v1.3.0Compare 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
OverlappingTLSConfigcondition 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
BackendTLSPolicySubjectAltNamesfrom Core to ExtendedSubjectAltNamesfield ofBackendTLSPolicychanged from Core to Extended feature. (#3591,@mlavacca)The
backendReffilter must send traffic to the correct backends when weighted routing is configuredbackendReffilters don't affect weighted routing. (#3604,@dprotaso)Clarify reasons for certain object status conditions
parametersRefAcceptedcondition whenparametersRefis invalid. (#3579,@mlavacca)GatewayClassReasonInvalidParametersreason description. (#3553,@mlavacca)BackendTLSPolicy
BackendTLSPolicy. (#3496,@snorwin)GRPCRoute
GRPCRoutematch limit from 8 -> 64 (#3601,@EyalPazz)Gateway.Spec.Addresses changes
A new type
GatewaySpecAddressreplacesGatewayAddress. InGatewayAddresstheValuefield was required. InGatewaySpecAddresstheValuefield is optional. When theValueis unspecified, if an implementation supports that,it SHOULD automatically assign an address. If an implementation does not support an empty
Value, it MUST set theProgrammedcondition in status to false with a reason of "AddressNotAssigned". TheAddressesfield inGateway.Spechas changed from type[]GatewayAddressto[]GatewaySpecAddress.valuefield inGateway.Spec.Addressesarray 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
HTTPRouteand
GRPCRouteobjects.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
supportedFeaturesfield in thestatusof 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
Xand 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.ioAPI 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.AllowCredentialsto 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
ListenerSethas changed toXListenerSet.The object group name has changed from
gateway.networking.k8s.iotogateway.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:
ListenerSets across namespaces (#3632,@dprotaso)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.