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

[gardener-github-actions]

Release Notes:

[github.com/gardener/machine-controller-manager:v0.59.0]

[gardener/machine-controller-manager]

✨ New Features

• [OPERATOR] machine-controller-manager can manage machines without a target cluster by specifying --target-kubeconfig=none. See the documentation for more details. by @timebertt [#1004]

🐛 Bug Fixes

• [OPERATOR] Fix a bug where MCM does not check if a pod has already been evicted before reattempting eviction blindly by @aaronfern [#979]
• [OPERATOR] Fixed a bug in the MachineSet controller where the machine status was set to Terminating even if attempt to delete the machine object failed. by @takoverflow [#995]

🏃 Others

• [OPERATOR] add new label node_name to the mcm_machine_info metric by @aaronfern [#1000]
• [OPERATOR] machine-controller-manager base image is updated to gcr.io/distroless/static-debian12:nonroot. by @aaronfern [#991]

Container (OCI) Images

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

[github.com/gardener/machine-controller-manager:v0.60.0]

✨ New Features

• [OPERATOR] When running without a target cluster machine-controller-manager will report a new status field addresses by @maboehm [#1012]
• [OPERATOR] Machine Class now has VirtualCapacity field hat maps to WorkerPool's NodeTemplate VirtualCapacity. by @elankath [#1024]

🐛 Bug Fixes

• [OPERATOR] Fixed metric mcm_machine_set_failed_machines and underlying variable *machineSet.Status.FailedMachines so that they reflect the current state of machines by @gagan16k [#1025]
• [USER] Fixed checking of createMachineTimeout when machine is Pending by @thiyyakat [#1015]
• [OPERATOR] Fixed a bug where machines in the InPlaceUpdating phase were incorrectly transferred to the new machine set during inplace updates. This caused the machine controller to miss updating the phase to InPlaceUpdateSuccessful, resulting in machines getting stuck or marked as InPlaceUpdateFailed. by @acumino [#1020]

🏃 Others

• [OPERATOR] node.gardener.cloud/critical-components-not-ready taint is added to the node after the successful in-place update to prevent scheduling any workload before critical component pods are ready. by @acumino [#1017]
• [OPERATOR] export testresults as inlined ocm-resource by @heldkat [#1022]
• [DEVELOPER] migrate CICD-Pipeline to GitHub-Actions by @ccwienk [#1011]
• [OPERATOR] Add informational logging for MachineDeployment rollout events by @gagan16k [#1029]
• [DEVELOPER] Convert .reuse/dep5 to REUSE.toml. by @thiyyakat [#1026]

[github.com/gardener/machine-controller-manager:v0.60.1]

🐛 Bug Fixes

• [OPERATOR] Added a safeguard to delay deletion of machines that are undergoing a Create Request to prevent orphaning of VMs. by @takoverflow [#1045]

[github.com/gardener/machine-controller-manager:v0.60.2]

🐛 Bug Fixes

• [OPERATOR] Fix panic if provider does not support Driver.InitializeMachine by @maboehm [#1047]

BoM Diff

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

Changed Components:

⚙ github.com/gardener/machine-controller-manager: v0.58.0 → v0.60.2

Component Details:

⚙ github.com/gardener/machine-controller-manager:v0.58.0 → v0.60.2

Resource	Version Change
➕ gosec-report	v0.60.2
➕ test-results	v0.60.2
➕ release-notes-archive	v0.60.2
➖ check-build-step-log	v0.58.0
🔄 machine-controller-manager	v0.58.0 → v0.60.2
🔄 release-notes	v0.58.0 → v0.60.2

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close

/lifecycle rotten