Bump github.com/gardener/gardener from 1.90.2 to 1.91.2

[dependabot[bot]]

Bumps github.com/gardener/gardener from 1.90.2 to 1.91.2.

Release notes

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

v1.91.2

[gardener/gardener]

🐛 Bug Fixes

• [OPERATOR] Fix bug where dependency watchdog is missing permissions to read nodes in the shoot clusters. by @​vpnachev #9503

Docker Images

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

v1.91.1

[gardener/dependency-watchdog]

🏃 Others

• [OPERATOR] dependency-watchdog-prober now skips Leases in the kube-node-lease namespace in case the corresponding Node does not exist (anymore). by @​rfranzkegardener/dependency-watchdog#108

Docker Images

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

v1.91.0

[gardener/gardener]

⚠️ Breaking Changes

• [USER] Deprecated .spec.kubernetes.allowPrivilegedContainers field in the Shoot API is now removed. by @​shafeeqes #9274
• [USER] The .status.advertisedAddresses[] list in a Shoot's status now includes the Shoot's service account issuer under the name service-account-issuer. Please revisit any logic that might depend on all advertised addresses being used for communication with the kube-apiserver of a shoot cluster. by @​dimityrmirchev #9196
• [OPERATOR] The ShootForceDeletion feature gate has been promoted to beta and is turned on by default. by @​acumino #9325

✨ New Features

• [DEVELOPER] The {garden,seed,shoot}-care controllers now incorporate ManagedResources into all relevant conditions, and it is possible to override the condition type into which a ManagedResource's status gets incorporated via the care.gardener.cloud/condition-type label. Please consult the respective documentation for more information (garden-care, seed-care, shoot-care). by @​rfranzke #9313
• [OPERATOR] The gardenlet now synchronizes the service account public keys of shoot clusters that have managed issuer enabled. The public keys are stored in a dedicated gardener-system-shoot-issuer namespace in the Garden cluster. by @​dimityrmirchev #9354
• [OPERATOR] gardener-resource-manager now considers the health and the progressing status for Certificate and Issuer resources (see cert-management) managed via ManagedResources. by @​timuthy #9326
• [OPERATOR] The Shoot maintenance controller now removes unsupported feature gates and admission plugins from the Shoot during force upgrades. by @​shafeeqes #9365
• [OPERATOR] gardener-operator now deploys two Alertmanager replicas into the garden namespace. They don't come with any configuration by default. It is in the responsibility of the human operators to create monitoring.coreos.com/v1alpha1.AlertmanagerConfig resources with the proper configuration suitable for their needs. Read more about it here. by @​rfranzke #9301
• [OPERATOR] The ControlPlaneHealthy condition in Shoots now reports an issue when {kube,machine}-controller-manager or cluster-autoscaler are scaled down to 0 replicas. The EveryNodeReady condition in Shoots now reports an issue when at least 20% of the Leases related to nodes in the kube-node-lease namespace are expired. by @​rfranzke #9376

... (truncated)

Commits

• 9661a7d Release v1.91.2
• 85822da [release-v1.91] FIx dependency-watchdog permissions (#9503)
• 9d89ebd Prepare next Development Cycle v1.91.2-dev
• a34b7cb Release v1.91.1
• 4b6c67b Upgrade dependency-watchdog (#9475)
• 2d4e4f7 Prepare next Development Cycle v1.91.1-dev
• df6b9c1 Release v1.91.0
• 5e4ffa3 Fix race condition in istio zone migration. (#9460)
• 11da203 Fix kube-apiserver service exposure after replacement of ingress resources wi...
• 2c61b00 Update dependency prometheus/prometheus to v2.51.0 (#9448)
• 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.

[gardener-robot]

@dependabot[bot] You need rebase this pull request with latest master branch. Please check.

[dependabot[bot]]

Looks like github.com/gardener/gardener is up-to-date now, so this is no longer needed.