Bump github.com/gardener/gardener from 1.89.0 to 1.90.1

[dependabot[bot]]

Bumps github.com/gardener/gardener from 1.89.0 to 1.90.1.

Release notes

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

v1.90.1

[gardener/gardener]

🐛 Bug Fixes

• [USER] A bug has been fixed which prevented Shoots using Alertmanager from getting stuck in reconciliation with error last error: more than one PV found with label disk-migration.monitoring.gardener.cloud/pvc-name=alertmanager-db-alertmanager-0. by @​rfranzke #9341
• [USER] A bug has been fixed which reported false negative health checks for the ObservabilityComponentsHealthy condition on Shoots using Alertmanager if they have been reconciled with Gardener >= 1.90. by @​rfranzke #9340
• [USER] An issue has been fixed which was causing scale-downs of kube-controller-manager and similar controllers due to prevented deletion of orphaned node Leases. by @​rfranzke #9351
• [OPERATOR] A bug causing the gardener-resource-manager configmap to be garbage collected because of missing reference annotation is now fixed. by @​aaronfern #9347
• [OPERATOR] An issue causing the reconciliation of backupentries to be stuck when the extension fails to populate the status is now fixed. by @​shafeeqes #9336

🏃 Others

• [OPERATOR] The skaffold version is downgraded from v2.10.1 to v2.9.0 to fix an issue with skaffold not detecting code changes on make gardener-up. by @​dimityrmirchev #9328
• [OPERATOR] NodeNotHealthy prometheus alert disregards nodes with deployment.machine.sapcloud.io/prefer-no-schedule taint by @​adenitiu #9346

Docker Images

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

v1.90.0

[gardener/gardener]

⚠️ Breaking Changes

• [OPERATOR] The UseGardenerNodeAgent feature gate has been promoted 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 @​rfranzke #9208
• [OPERATOR] ⚠️ Gardener does no longer support garden, seed, or shoot clusters with Kubernetes versions == 1.24. Make sure to upgrade all existing clusters before upgrading to this Gardener version. by @​shafeeqes #8989
• [OPERATOR] The APIServerFastRollout feature gate has been promoted 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 @​oliver-goetz #9214
• [DEVELOPER] The pkg/envtest package has been moved to test/envtest. Most component packages in pkg/component have been moved. The pkg/openapi and pkg/registry packages have been moved to pkg/apiserver/*. by @​rfranzke #9217
• [DEVELOPER] Function signature of infrastructure controller NewReconciler has changed from NewReconciler(manager.Manager, Actuator, ConfigValidator) to NewReconciler(manager.Manager, Actuator, ConfigValidator, map[gardencorev1beta1.ErrorCode]func(string) bool). by @​acumino #9321
• [USER] The spec.kubernetes.allowPrivilegedContainers field in the Shoot API is deprecated and will be removed in a future version. This field is not relevant to Shoots with kubernetes versions >= 1.25. Please adapt your controllers accordingly. by @​shafeeqes #8989

📰 Noteworthy

• [USER] It is no longer possible to add or change the .spec.seedSelector field in Shoots when spec.seedName is already set. by @​rfranzke #9212

✨ New Features

• [OPERATOR] DNSRecord resources for seed and shoot clusters now have an annotation indicating their target ip stack (dns.gardener.cloud/ip-stack set to either ipv4, ipv6, or dual-stack). by @​ScheererJ #9289
• [OPERATOR] gardener-resource-manager's health check controller now checks whether VerticalPodAutoscalers report the ConfigUnsupported condition. by @​rfranzke #9211
• [USER] It is now possibleto specify some cluster-autoscaler related options per worker pool in Shoots via spec.provider.workers[].clusterAutoscaler. Read more about it here. by @​aaronfern #9245
• [USER] In order to fine-tune VPA CPU recommendations, the CPU target percentile parameter for vpa-recommender can now be configured in the Shoot specification via the .spec.kubernetes.verticalPodAutoscaler.targetCPUPercentile field. by @​voelzmo #9279
• [DEVELOPER] It is now possible to provide configuration for the aggregate Prometheus running in seed clusters' garden namespaces. Read all about it here. by @​rfranzke #9200

🐛 Bug Fixes

• [DEPENDENCY] An issue was fixed that sometimes led to leaked extension-controlplane-shoot-webhooks which blocked the shoot deletion. by @​timuthy #9209
• [DEPENDENCY] hack/hook-me.sh now ensures the required network connectivity so that the quic tunnel can be successfully established. by @​vpnachev #8909

... (truncated)

Commits

• ed24bad Release v1.90.1
• e7a4a1b Parallelize orphaned node Lease deletion (#9351)
• aebc096 add task to delete dwd mr and secret in shoot deletion flow (#9348)
• df92606 Injected new reference annotations when updating grm cm on gardenletr startup...
• bbd302b [release-v1.90] Refine NodeNotHealthy prometheus alert (#9346)
• 7d02f74 [release-v1.90] [GEP-19] Add dedicated namespace label for PVCs in migration ...
• bbabd81 Check for alertmanager-shoot when Gardener >= 1.90 (#9340)
• 35ad44d Reconcile extension if lastOperation is nil (#9336)
• fe41fbd Downgrade skaffold to v2.9.0 (#9328)
• 960125b Prepare next Development Cycle v1.90.1-dev
• 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 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)

[gardener-robot]

@dependabot[bot] Thank you for your contribution.

[gardener-robot-ci-2]

Thank you @dependabot[bot] for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

[MrBatschner]

/add reviewed/ok-to-test