[ci:component:github.com/gardener/machine-controller-manager:v0.53.0->v0.55.0]

[gardener-robot-ci-2]

BoM Diff

Added components: 0
Changed components: 1
Removed components: 0

Changed Components:

⚙ github.com/gardener/machine-controller-manager: v0.53.0 → v0.55.0

Component Details:

⚙ github.com/gardener/machine-controller-manager:v0.53.0 → v0.55.0

Resource	Version Change
🔄 machine-controller-manager	v0.53.0 → v0.55.0

Release Notes:

The following dependencies are updated:
- `k8s.io/*` : `v0.29.3` -> `v0.31.0`

MCM replaces the magic string `<<MACHINE_NAME>>` in user data with the name of the machine when it is bootstrapped.

golangci-lint will now be used as the linter instead of the older golint

Removed support for v1beta1 PDBs

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.

Fixed a bug where failure of machine initialization caused label updates to not happen. 

Golang version used is now upgraded to `1.22.5`

Fixed a bug where the `Unitialised` error code was blocking machine deletion

MCM will use an `informer` instead of the`clientset` to list pods in the drain logic. This will reduce the load on etcd/kube-apiserver.

Broken API doc links are now fixed

Fixed bug that removed the shoot-- prefix from control cluster namespace for integration tests using the gardener local setup case

MCM adds the name of the machine to `node.gardener.cloud/machine-name` label of the corresponding node.

Drain timeout is now correctly honored for Pod eviction during Machine Drain

`getVMStatus` always redirects to `InitiateDrain`. It also populates the node label on the machine object by checking `node.gardener.cloud/machine-name` label on the nodes. 

Fixed a bug in drain logic where volume reattachment context declaration used incorrect parent context

Adding `gosec` for Static Application Security Testing (SAST).

MCM recognizes scaling-up of `machineDeployment` from 0 to more replicas as a scaling event rather than a rolling update.

[gardener-robot]

@gardener-robot-ci-2 Thank you for your contribution.