fix(deps): update module sigs.k8s.io/gateway-api to v1.4.1#2354
Closed
renovate-sh-app[bot] wants to merge 1 commit intomasterfrom
Closed
fix(deps): update module sigs.k8s.io/gateway-api to v1.4.1#2354renovate-sh-app[bot] wants to merge 1 commit intomasterfrom
renovate-sh-app[bot] wants to merge 1 commit intomasterfrom
Conversation
| datasource | package | from | to | | ---------- | ----------------------- | ------ | ------ | | go | sigs.k8s.io/gateway-api | v1.3.0 | v1.4.1 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
renovate-sh-app
Bot
requested review from
Baarsgaard,
hubeadmin,
ishanjainn,
nissessenap,
pb82,
theSuess and
weisdd
as code owners
Collaborator
|
The kubebuilder annotation fix (kubernetes-sigs/gateway-api#4158) did not make it into v1.4.1, so closing the PR. |
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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
1 participant
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.3.0->v1.4.1Release Notes
kubernetes-sigs/gateway-api (sigs.k8s.io/gateway-api)
v1.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.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
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 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.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.