chore(deps): update module sigs.k8s.io/gateway-api to v1.1.0

gardener-ci-robot commented 1 month ago

This PR contains the following updates:

Package	Type	Update	Change
sigs.k8s.io/gateway-api	require	minor	`v1.0.0` -> `v1.1.0`

Release Notes

kubernetes-sigs/gateway-api (sigs.k8s.io/gateway-api)

### [`v1.1.0`](https://togithub.com/kubernetes-sigs/gateway-api/releases/tag/v1.1.0) [Compare Source](https://togithub.com/kubernetes-sigs/gateway-api/compare/v1.0.0...v1.1.0) ### v1.1.0 On behalf of Kubernetes SIG Network, we are pleased to announce the v1.1 release! This release includes the graduation of several features to GA, including both GRPCRoute and Service Mesh. We are also introducing several new experimental features, including Session Persistence and Gateway Client Cert Verification. The following represents the changes since v1.0.0: #### Standard Channel ##### GRPCRoute has Graduated to GA 🎉 GRPCRoute has graduated to GA (v1) and is now part of the Standard Channel. If you are already using the experimental version GRPCRoute, we recommend holding off on upgrading to the standard channel version of GRPCRoute until the controllers you're using have been updated to support GRPCRoute v1. Until then, it is safe to upgrade to the experimental channel version of GRPCRoute in v1.1 that includes both v1alpha2 and v1 API versions. Leading Contributor: [@gnossen](https://togithub.com/gnossen) ##### Service Mesh Support has Graduated to GA 🎉 The standard for using Gateway API for Mesh has formally graduated to GA (v1) and is now part of the Standard Channel. Service mesh support in Gateway API allows service mesh users to use the same API to manage ingress traffic and mesh traffic, reusing the same policy and routing interfaces. In Gateway API v1.1, routes (such as HTTPRoute) can now have a `Service` as a `parentRef`, to control how traffic to specific services behave. For more information, read the [service mesh](https://gateway-api.sigs.k8s.io/mesh/) documentation or see the list of [implementations](https://gateway-api.sigs.k8s.io/implementations/#service-mesh-implementation-status). Leading Contributors: [@howardjohn](https://togithub.com/howardjohn), [@keithmattix](https://togithub.com/keithmattix), [@kflynn](https://togithub.com/kflynn), [@mikemorris](https://togithub.com/mikemorris) ##### Conformance Profiles and Reports The Conformance Reports API and the corresponding test suite have been graduated to GA. The Conformance report API has been expanded with the `mode` field (intended to specify the working mode of the implementation), and the `gatewayAPIChannel` (standard or experimental). The `gatewayAPIVersion` and `gatewayAPIChannel` are now filled in automatically by the suite machinery, along with a brief description of the testing outcome. The Reports have been reorganized in a more structured way, and the implementations can now add information on how the tests have been run and provide reproduction steps. Leading Contributors: [@mlavacca](https://togithub.com/mlavacca), [@shaneutt](https://togithub.com/shaneutt) ##### ParentRef Port field Graduated to GA The `port` field in ParentRefs has graduated to GA (v1) and is now part of the Standard Channel. You can use the `port` field to attach resources to Gateways, Services, or other parent resources. For example, you can attach an HTTPRoute to one or more specific Listeners of a Gateway based on the Listener `port`, instead of `name` field. Leading Contributor: [@frankbu](https://togithub.com/frankbu) #### Experimental Channel ##### Session Persistence + BackendLBPolicy Session Persistence is being introduced to Gateway API via a new policy (BackendLBPolicy) for Service-level configuration and as fields within HTTPRoute and GRPCRoute for Route-level configuration. The BackendLBPolicy and Route-level APIs provide the same session persistence configuration, including session timeouts, session name, session type, and cookie lifetime type. Leading Contributors: [@gcs278](https://togithub.com/gcs278), [@ginayeh](https://togithub.com/ginayeh) ##### Gateway Client Cert Verification Gateways can now configure client cert verification for each Gateway Listener by introducing a new field `frontendValidation` field within `tls`. This field supports configuring a list of CA Certificates that can be used as a trust anchor to validate the certificates presented by the client. Leading Contributors: [@arkodg](https://togithub.com/arkodg) ##### BackendTLSPolicy As part of a broader goal of making our TLS terminology more consistent throughout the API, we've introduced some breaking changes to BackendTLSPolicy. This has resulted in a new API version (v1alpha3) and will require any existing users of this policy to uninstall the v1alpha2 version before installing this newer version. Any references to v1alpha2 BackendTLSPolicy fields will need to be updated. Specific changes include: - the `targetRef` field is now a `targetRefs` list and these references no longer include a `namespace` field. - the `tls` field has been renamed to `validation` - the `caCertRefs` field has been renamed to `caCertificateRefs` - the `wellKnownCACerts` field has been renamed to `wellKnownCACertificates` Leading Contributors: [@candita](https://togithub.com/candita) ##### Gateway Params Gateways now feature a new field that allows references to implementation-specific parameters, similar to GatewayClass. Leading Contributors: [@howardjohn](https://togithub.com/howardjohn) #### Everything Else ##### gwctl - We've extended the `get` command to support gateways, gatewayclasses, and namespaces. ([#2865](https://togithub.com/kubernetes-sigs/gateway-api/issues/2865), [#2782](https://togithub.com/kubernetes-sigs/gateway-api/issues/2782), [#2847](https://togithub.com/kubernetes-sigs/gateway-api/issues/2847), [@jongwooo](https://togithub.com/jongwooo)) - The `get` command now provides more detailed information for httproutes, policies, and policycrds. ([#2805](https://togithub.com/kubernetes-sigs/gateway-api/issues/2805), [#2808](https://togithub.com/kubernetes-sigs/gateway-api/issues/2808), [#2811](https://togithub.com/kubernetes-sigs/gateway-api/issues/2811), [@jongwooo](https://togithub.com/jongwooo)) - `describe` command now supports descriptions of policycrds and namespaces. ([#2872](https://togithub.com/kubernetes-sigs/gateway-api/issues/2872), [#2836](https://togithub.com/kubernetes-sigs/gateway-api/issues/2836), [@Devaansh-Kumar](https://togithub.com/Devaansh-Kumar)) - We've added the ability to filter resources using labels (through the `-l` flag) with both the `get` and `describe` commands. ([#2892](https://togithub.com/kubernetes-sigs/gateway-api/issues/2892), [#2915](https://togithub.com/kubernetes-sigs/gateway-api/issues/2915), [#2934](https://togithub.com/kubernetes-sigs/gateway-api/issues/2934), [@yeedove](https://togithub.com/yeedove)) - Bug fix: Prevent panic when describing gatewayclasses with no description ([#2894](https://togithub.com/kubernetes-sigs/gateway-api/issues/2894), [@pmalek](https://togithub.com/pmalek)) - Properly handle different API versions ([#3001](https://togithub.com/kubernetes-sigs/gateway-api/issues/3001), [@gauravkghildiyal](https://togithub.com/gauravkghildiyal)) - Provide more detail in describe output ([#2999](https://togithub.com/kubernetes-sigs/gateway-api/issues/2999), [@gauravkghildiyal](https://togithub.com/gauravkghildiyal)) - Support JSON and YAML output format in get commands ([#2940](https://togithub.com/kubernetes-sigs/gateway-api/issues/2940), [@yashvardhan-kukreja](https://togithub.com/yashvardhan-kukreja)) ##### Validation Changes - TLS Configuration is no longer required on Gateway Listeners to enable more flexible TLS configuration. ([#2721](https://togithub.com/kubernetes-sigs/gateway-api/issues/2721), [@robscott](https://togithub.com/robscott)) ##### Conformance Tests - Conformance Profiles have been renamed and a new `Mesh-GRPC` profile has been added ([#3019](https://togithub.com/kubernetes-sigs/gateway-api/issues/3019), [@mlavacca](https://togithub.com/mlavacca)): - HTTP -> Gateway-HTTP - GRPC -> Gateway-GRPC - TLS -> Gateway-TLS - Mesh -> Mesh-HTTP - Fixed GatewayWithAttachedRoutes conformance test to not check that the HTTPRoute status includes an "Accepted: False" condition because this is not required by the specification. ([#2548](https://togithub.com/kubernetes-sigs/gateway-api/issues/2548), [@frankbu](https://togithub.com/frankbu)) - A new comparison view has been added to our documentation that shows the extended features supported by every implementation that has submitted a conformance report ([#2874](https://togithub.com/kubernetes-sigs/gateway-api/issues/2874), [@xtineskim](https://togithub.com/xtineskim)) - Added SupportMeshConsumerRoute and SupportMeshClusterIPMatching supported features to more clearly communicate the purpose of existing Mesh conformance tests ([#3035](https://togithub.com/kubernetes-sigs/gateway-api/issues/3035), [@howardjohn](https://togithub.com/howardjohn)) - Add conformance test for HTTP listener isolation ([#3047](https://togithub.com/kubernetes-sigs/gateway-api/issues/3047), [@arkodg](https://togithub.com/arkodg), [@pleshakov](https://togithub.com/pleshakov)) ##### Dependencies - Gateway API has upgraded to Go v1.22 and Kubernetes v1.30 ([#2988](https://togithub.com/kubernetes-sigs/gateway-api/issues/2988), [@robscott](https://togithub.com/robscott)) ##### Cleanup - The validating webhook has been removed. CEL validation is now built-in to CRDs and replaces the webhook. ([#2595](https://togithub.com/kubernetes-sigs/gateway-api/issues/2595), [@robscott](https://togithub.com/robscott)) - BackendTLSPolicy WellKnownCACerts field has been updated to implementation-specific support ([#2741](https://togithub.com/kubernetes-sigs/gateway-api/issues/2741), [@sunjayBhatia](https://togithub.com/sunjayBhatia)) - Clarify policy attachment by two of the same policy types when using section names. ([#2442](https://togithub.com/kubernetes-sigs/gateway-api/issues/2442), [@maleck13](https://togithub.com/maleck13)) - Remove v1alpha2 directory from docs: ([#2965](https://togithub.com/kubernetes-sigs/gateway-api/issues/2965), [@robscott](https://togithub.com/robscott))

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.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

gardener-ci-robot commented 1 month ago

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

9 additional dependencies were updated

Details:

Package	Change
`k8s.io/api`	`v0.29.7` -> `v0.30.0`
`k8s.io/apiextensions-apiserver`	`v0.29.7` -> `v0.30.0`
`k8s.io/apimachinery`	`v0.29.7` -> `v0.30.0`
`k8s.io/client-go`	`v0.29.7` -> `v0.30.0`
`k8s.io/code-generator`	`v0.29.7` -> `v0.30.0`
`sigs.k8s.io/controller-runtime`	`v0.17.5` -> `v0.18.0`
`github.com/evanphx/json-patch/v5`	`v5.8.0` -> `v5.9.0`
`k8s.io/component-base`	`v0.29.7` -> `v0.30.0`
`sigs.k8s.io/controller-tools`	`v0.14.0` -> `v0.15.0`

gardener-prow[bot] commented 1 month ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign martinweindel for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/gardener/cert-management/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

gardener-prow[bot] commented 1 month ago

@gardener-ci-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cert-management-unit	e88ff325ac23234900a8acbad9442a8cc11d4806	link	true	`/test pull-cert-management-unit`
pull-cert-management-e2e-kind	e88ff325ac23234900a8acbad9442a8cc11d4806	link	true	`/test pull-cert-management-e2e-kind`

Full PR test history. Your PR dashboard. Command help for this repository. Please help us cut down on flakes by linking this test failure to an open flake report or filing a new flake report if you can't find an existing one. Also see our testing guideline for how to avoid and hunt flakes.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

MartinWeindel commented 1 month ago

/close stay with same version as gardener/gardener

gardener-ci-robot commented 1 month ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.1.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

gardener / cert-management