search

kyma-project / control-plane

A flexible and easy way to manage Kyma Runtimes
Apache License 2.0
17 stars 113 forks source link

gomod(deps): bump github.com/gardener/gardener-extension-provider-gcp from 1.33.1 to 1.34.1 in /components/kyma-metrics-collector #3350

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps github.com/gardener/gardener-extension-provider-gcp from 1.33.1 to 1.34.1.

Release notes

Sourced from github.com/gardener/gardener-extension-provider-gcp's releases.

v1.34.1

[gardener/gardener-extension-provider-gcp]

🏃 Others

  • [OPERATOR] Admission controller will be deployed with the LEADER_ELECTION_NAMESPACE set to the pod namespace by @​kon-angelo #700
  • [OPERATOR] Enable storage pool in CSI driver by @​kon-angelo #698

Docker Images

  • gardener-extension-admission-gcp: europe-docker.pkg.dev/gardener-project/releases/gardener/extensions/admission-gcp:v1.34.1
  • gardener-extension-provider-gcp: europe-docker.pkg.dev/gardener-project/releases/gardener/extensions/provider-gcp:v1.34.1

v1.34.0

[gardener/gardener-extension-provider-gcp]

⚠️ Breaking Changes

  • [OPERATOR] CA and server certificates for the admission component are managed automatically. Passing custom certificates via Helm values is not supported anymore. by @​timuthy #675

📰 Noteworthy

  • [OPERATOR] Tagging the 'default' StorageClass and VolumeSnapshotClass as default can now be disabled. by @​AndreasBurger #687
  • [USER] Disks, boot disks, and instances will now share a common label 'k8s-cluster-name' that contains the shoot-ID.
    Also, user-provided labels will now be added to boot disks as well. by @​AndreasBurger #669

✨ New Features

🏃 Others

  • [OPERATOR] fix unknown flag --gardenlet-manages-mcm by @​tedteng #690
  • [OPERATOR] Newly provisioned disks by the GCP CSI driver will now have a label k8s-cluster-name=<shoot-technical-id>. The label makes possible finding the owning Shoot cluster for a GCP disk. by @​ialidzhikov #660
  • [OPERATOR] Update csi-driver to v1.13.0 by @​kon-angelo #685
  • [OPERATOR] Vendor gardener v1.87.1 by @​kon-angelo #694
  • [OPERATOR] The code related to machine-controller-manager management has been cleaned up because gardenlet is responsible for it since gardener/gardener@v1.83. by @​kon-angelo #691
  • [OPERATOR] Bump github.com/gardener/gardener to 1.86.0. by @​timuthy #675
  • [DEVELOPER] The vendor directory was removed in favor of the go mod cache. by @​timuthy #675
  • [DEVELOPER] Add new unit tests. by @​axel7born #664

[gardener/machine-controller-manager]

⚠️ Breaking Changes

  • [OPERATOR] Change OCI Image Registry from GCR (eu.gcr.io/gardener-project) to Artifact-Registry (europe-docker.pkg.dev/gardener-project/releases). Users should update their references. by @​ccwienkgardener/machine-controller-manager#878

🐛 Bug Fixes

  • [DEVELOPER] MCM restart happens properly in integration tests now. This fix will get activated, once this version is vendored in your mcm-provider by @​sssash18gardener/machine-controller-manager#879
  • [DEVELOPER] A bug in UpdateNodeToMachine which cause the IT to fail is fixed. by @​gardener-robot-ci-1gardener/machine-controller-manager#106
  • [OPERATOR] Fix for edge case of Node object deletion missed during machine termination. by @​elankathgardener/machine-controller-manager#887

🏃 Others

  • [OPERATOR] machine controller won't reconcile machine on non-spec update events by @​himanshu-kungardener/machine-controller-manager#877

... (truncated)

Commits


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)