Bump github.com/gardener/gardener from 1.115.1 to 1.116.1

[dependabot]

Fixes #381

---

Bumps github.com/gardener/gardener from 1.115.1 to 1.116.1.

Release notes

Sourced from github.com/gardener/gardener's releases.

v1.116.1

[gardener/gardener]

🐛 Bug Fixes

• [USER] An issue causing the cloudprovider Secret to contain both static credentials and workload identity config, which are mutually exclusive, when migrating to workload identity is now fixed. by @​dimityrmirchev #11847
• [DEVELOPER] Fix malformed file path error on go get github.com/gardener/[email protected] by @​MartinWeindel #11820

Helm Charts

• controlplane: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/controlplane:v1.116.1
• gardenlet: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/gardenlet:v1.116.1
• operator: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/operator:v1.116.1
• resource-manager: europe-docker.pkg.dev/gardener-project/releases/charts/gardener/resource-manager:v1.116.1

Docker Images

• admission-controller: europe-docker.pkg.dev/gardener-project/releases/gardener/admission-controller:v1.116.1
• apiserver: europe-docker.pkg.dev/gardener-project/releases/gardener/apiserver:v1.116.1
• controller-manager: europe-docker.pkg.dev/gardener-project/releases/gardener/controller-manager:v1.116.1
• gardenlet: europe-docker.pkg.dev/gardener-project/releases/gardener/gardenlet:v1.116.1
• node-agent: europe-docker.pkg.dev/gardener-project/releases/gardener/node-agent:v1.116.1
• operator: europe-docker.pkg.dev/gardener-project/releases/gardener/operator:v1.116.1
• resource-manager: europe-docker.pkg.dev/gardener-project/releases/gardener/resource-manager:v1.116.1
• scheduler: europe-docker.pkg.dev/gardener-project/releases/gardener/scheduler:v1.116.1

v1.116.0

[gardener/gardener]

⚠️ Breaking Changes

• [DEVELOPER] /hack/generate-crds.sh will no longer generate any CRDs with group=druid.gardener.cloud. One must use etcd-druid API to get the CRDs that serve as a single source of truth for all etcd-druid CRDs. by @​unmarshall #11545
• [DEVELOPER] The extension class field in the generic extension controller was removed. Please use the new field classes instead. by @​timuthy #11764
• [OPERATOR] The etcd-druid's GA-ed UseEtcdWrapper feature gate is removed. It is now unconditionally enabled. It should no longer be passed in gardenlet configuration. Before upgrading to this version of Gardener, check your gardenlet configuration and make sure that it does not specify the etcd-druid's UseEtcdWrapper feature gate. by @​unmarshall #11545
• [OPERATOR] The default etcd-main storage is increased from 10Gi to 25Gi. The etcd-main storage capacity is mutated by provider extensions. Before upgrading to this version of Gardener, make sure the provider extensions which you use mutate the etcd-main capacity. Otherwise, the default storage capacity change in Gardener could be unexpected or breaking. by @​unmarshall #11545
• [OPERATOR] Please note, if you configure spec.extensions in your Garden resource: gardener-operator adds a garden- prefix to all extension resources configured via the Garden. Existing extension resources (not prefixed) will be deleted automatically at the end of the reconciliation. Another, manually triggered Garden reconciliation might be required to reach the desired state of the extension again. by @​timuthy #11764

📰 Noteworthy

• [OPERATOR] NodeAgentAuthorizer feature gate has been promoted to beta and is now enabled by default. by @​oliver-goetz #11757
• [OPERATOR] The feature gate NewVPN has been graduated to GA. It was already enabled by default and can now no longer be turned off. The feature gate will be removed in a future release. by @​domdom82 #11714

✨ New Features

• [OPERATOR] Extensions can be configured for Seeds via spec.extensions to deploy extensions for the seed cluster. Before activating this configuration, please first confirm that the corresponding extension is compatible with the seed use-case. by @​timuthy #11764

🐛 Bug Fixes

• [OPERATOR] The NetworkPolicy controller part of gardener-resource-manager does no longer attempt to create resources in terminating namespaces. by @​rfranzke #11808
• [OPERATOR] An issue causing Shoot reconciliation to fail with no relationship found when the referenced SecretBinding/CredentialsBinding is forcefully deleted (its finalizer is removed by the end user) and then recreated with the same name is now fixed. gardener-admission-controller's authorisation graph is now updated for a Shoot after forceful deletion and recreation of the referenced Secretbinding/CredentialsBinding. by @​MartinWeindel #11461
• [OPERATOR] If the computed pod label selector contains keys exceeding 63 characters, the NetworkPolicy controller part of gardener-resource-manager does now shorten them to make sure they can actually get created. Previously, it failed trying to create them infinitely, resulting in high CPU load in large clusters. by @​rfranzke #11808
• [OPERATOR] Keep operator.gardener.cloud.Extension condition RequiredRuntime = true until deletion of extensions.gardener.cloud.Extensions has completed. by @​MartinWeindel #11696
• [OPERATOR] Fix a bug that appears when migrating a Shoot between Seeds by introducing a new controller, which manages a ShootState finalizer preventing early object deletions. by @​vitanovs #11491

🏃 Others

• [DEVELOPER] Remove the double maintenance of CRDs defined in etcd-druid. Now, gardenlet is using the etcd-druid CRD APIs to get the CRDs ensuring one single source of truth. by @​unmarshall #11545

... (truncated)

Commits

• 4d552d3 Release v1.116.1
• a77b339 Overwrite existing cloud provider secret data when using workload identity co...
• ddfe9f7 [release-v1.116] Fix malformed file path error on `go get github.com/gardener...
• 4ba50e4 Prepare next Development Cycle v1.116.1-dev
• 417c210 Release v1.116.0
• 5400174 Ensure cp namespace is deployped before src BackupEntry (#11811)
• c34ceb4 [release-v1.116] [resource-manager] Prevent infinite NetworkPolicy controll...
• 2586102 Fix the should copy data to pod VPN tunnel TM test (#11803)
• ec1cd56 Fix the Shoot logging TM tests (#11794)
• 68d1fa6 Patch ShootState integration tests addressing flakes when managing resource...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ialidzhikov]

/assign

[gardener-prow]

[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 ask for approval from ialidzhikov. For more information see the 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

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gardener-prow]

@dependabot[bot]: The following test 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-gardener-extension-registry-cache-e2e-kind	f624238	link	true	/test pull-gardener-extension-registry-cache-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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ialidzhikov]

The e2e test failure will be fixed by gardener/gardener#11008.
gardener/gardener#11701 (more concretely gardener/gardener@bfb1fe8) moves the hosts.toml files that provider-local contributes from the OSC to the host file system. Due to the existing issue that readiness probe of a registry config is not executed if the corresponding file exists, the new registry config is applied right away without readiness probes -> we end up with the Node bootstrap problem (image pull requests time out in 30s because kube-proxy is not yet running and iptables routes are not set up).

[dependabot]

A newer version of github.com/gardener/gardener exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[ialidzhikov]

/remove-lifecycle stale