You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[USER] Users with delete permissions can simply use kubectl delete node to delete backing Machine. node.machine.sapcloud.io/trigger-deletion-by-mcm annotation on Node no longer supported for indirect deletion of Machine by @gagan16k [#1055]
🐛 Bug Fixes
[OPERATOR] Fixed spurious warning logs for machines without force-deletion label by @gagan16k [#1057]
[OPERATOR] Made changes to reconcileClusterMachineTermination to avoid duplicate reconciliations by @r4mek [#1056]
[OPERATOR] Updated machineclass reconciliation to avoid unnecessary machine requeues by @r4mek [#1056]
[OPERATOR] Fix panic if provider does not support Driver.InitializeMachine by @maboehm [#1032]
[OPERATOR] The metric for the machine_current_status_phase has been fixed and is not reporting removed Machines anymore by @Duciwuci [#1058]
[OPERATOR] Added a safeguard to delay deletion of machines that are undergoing a Create Request to prevent orphaning of VMs. by @takoverflow [#1036]
[OPERATOR] Fixed an issue where deleting a machine from an old MachineSet could prevent proper scaling. The new MachineSet now scales up when total replicas (old + new) drop below the desired count, ensuring replacements are created with the updated configuration. by @acumino [#1052]
📖 Documentation
[DEVELOPER] Added proposal for the temporary preservation of machines. by @thiyyakat [#1031]