gardener / gardener-extension-shoot-cert-service

Gardener extension controller for certificate services for shoot clusters.
https://gardener.cloud
Apache License 2.0
10 stars 35 forks source link

Bump github.com/gardener/gardener from 1.90.0 to 1.90.2 #240

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

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

Release notes

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

v1.90.2

[gardener/gardener]

🐛 Bug Fixes

  • [USER] An issue has been fixed which caused Shoot reconciliation to get stuck because the API discovery used to generate the read-only ClusterRole for shoots/viewerkubeconfig subresource failed. by @​rfranzke #9361

Docker Images

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

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
Commits
  • af6dfc1 Release v1.90.2
  • 81befa6 [release-v1.90] Improve API discovery for generating read-only ClusterRole ...
  • 8b3ad7e Prepare next Development Cycle v1.90.2-dev
  • 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)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 commented 7 months ago

@dependabot[bot] Thank you for your contribution.

gardener-robot-ci-1 commented 7 months ago

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.

dependabot[bot] commented 7 months ago

Superseded by #241.