Bump github.com/gardener/machine-controller-manager from 0.54.0 to 0.55.0

[dependabot[bot]]

Bumps github.com/gardener/machine-controller-manager from 0.54.0 to 0.55.0.

Release notes

Sourced from github.com/gardener/machine-controller-manager's releases.

v0.55.0

[gardener/machine-controller-manager]

🐛 Bug Fixes

• [USER] MCM recognizes scaling-up of machineDeployment from 0 to more replicas as a scaling event rather than a rolling update. by @​thiyyakat #956
• [USER] A bug has been fixed for draining nodes with provider-unrelated volumes like NFS volumes. With this fix, the machine controller doesn't try to track their (non-existing) VolumeAttachments. by @​timebertt #937
• [OPERATOR] Fixed a bug in drain logic where volume reattachment context declaration used incorrect parent context by @​rishabh-11 #947

🏃 Others

• [OPERATOR] MCM will use an informer instead of theclientset to list pods in the drain logic. This will reduce the load on etcd/kube-apiserver. by @​thiyyakat #949
• [OPERATOR] Removed support for v1beta1 PDBs by @​rishabh-11 #947
• [DEVELOPER] Adding gosec for Static Application Security Testing (SAST). by @​thiyyakat #954

Docker Images

• machine-controller-manager: europe-docker.pkg.dev/gardener-project/releases/gardener/machine-controller-manager:v0.55.0

Commits

• 2add8db Release v0.55.0
• 341fad1 Fix edge-case where scale-from-zero of MCD is mistaken for a rolling update (...
• f17b00e Introduce gosec for Static Application Security Testing (SAST) (#954)
• 99b0276 Export magic userdata strings (#953)
• 31834e2 Reduce load on etcd/kube-apiserver on pod eviction (#949)
• e91182a Merge pull request #947 from rishabh-11/remove-shadow
• 109a923 Fixed broken links - 2024.10 (#946)
• 3a07275 remove support for v1beta1 PDBs
• fab4229 fix ctx declaration for vol detachment and reattachment
• 67e4579 Don't track reattachment of provider-unrelated PVs (#937)
• 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-ci-3]

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] Thank you for your contribution.