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

[gardener-robot-ci-1]

Release Notes:

Bump `k8s.io/*` deps to `v0.28.2`

The default `machine-safety-orphan-vms-period` has been reduced from 30m to 15m.

Fix for edge case of Node object deletion missed during machine termination.

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.

Architecture field added in the nodetemplate. This will allow CA to pickup architecture from machine class and schedule pods on relevant arch nodes.

MCM restart happens properly in integration tests now. This fix will get activated, once this version is vendored in your mcm-provider

machine controller won't reconcile machine on non-spec update events

go-git now removed from dependencies due to CVE's.

fixed IT for seed with k8s >= 1.27 as control cluster 

Removes `node.machine.sapcloud.io/not-managed-by-mcm` annotation from nodes managed by the MCM.

Phase transition diagram for a machine object is added to FAQs

[gardener-robot]

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

[elankath]

Local Integration Test run was finally successful after resolving misc issues. (CICD pipeline is yet available for openstack provider)

- Machine controllers test machine resource creation should not lead to any errors and add 1 more node in target cluster
- Machine controllers test machine resource deletion when machines available should not lead to errors and remove 1 node in target cluster
- Machine controllers test machine resource deletion when machines are not available should keep nodes intact
- Machine controllers test machine deployment resource creation with replicas=3 should not lead to errors and add 3 more nodes to target cluster
- Machine controllers test machine deployment resource scale-up with replicas=6 should not lead to errors and add futher 3 nodes to target cluster
- Machine controllers test machine deployment resource scale-down with replicas=2 should not lead to errors and remove 4 nodes from target cluster
- Machine controllers test machine deployment resource scale-down with replicas=2 should freeze and unfreeze machineset temporarily
- Machine controllers test machine deployment resource updation to v2 machine-class and replicas=4 should upgrade machines and add more nodes to target
- Machine controllers test machine deployment resource deletion When there are machine deployment(s) available in control cluster should not lead to errors and list only initial nodes
- Machine controllers test orphaned resources when the hyperscaler resources are queried should have been deleted

Ran 10 of 10 Specs in 1066.318 seconds
SUCCESS! -- 10 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS