chore(deps): update dependency gateway-api to v1.5.1#80
Open
pedrotchang wants to merge 1 commit into
Open
Conversation
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
2 participants
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.4.1→v1.5.1Release Notes
kubernetes-sigs/gateway-api (gateway-api)
v1.5.1Compare 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.1
Major Changes Since v1.5.0
GEP
Conformance
conflicted=falsecondition is not required anymore in the listener status for non-conflicted listeners. (#4664, @zhaohuabing)What's Changed
Full Changelog: kubernetes-sigs/gateway-api@v1.5.0...v1.5.1
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 XListenerSetTLSRoute and ListenerSet have graduated to the Standard channel as
v1. In 1.5.0, TLSRoutev1alpha2is present only in the Experimental channel; in 1.6, it will be removed from the Experimental channel too.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
5ec99f8Configuration
📅 Schedule: (UTC)
🚦 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 has been generated by Mend Renovate.