v0.48.0

[machine-controller-manager]

⚠️ Breaking Changes

• [USER] node field is removed from machine status. controller will now depend on the node label which already was present in the machine object's metadata. If you(or your controller) are dependent on the status.node field of the machine object, then kindly use node label under .metadata.labels (gardener/machine-controller-manager#745, @rishabh-11)

✨ New Features

• [USER] MachineDeployment would now have Progressing condition even when no progress Deadline is specified. This condition would never go to the reason ProgressDeadlineExceeded in that case. (gardener/machine-controller-manager#762, @himanshu-kun)
• [OPERATOR] Using kubectl get machines will display Node of the corresponding machine as a column. If -owide flag is used then the corresponding ProviderID will also be displayed. (gardener/machine-controller-manager#746, @rishabh-11)
• [OPERATOR] Added new short names for machine(mc), machineClass(mcc), machineDeployment(mcd), and machineSet(mcs) resources. (gardener/machine-controller-manager#749, @rishabh-11)

🏃 Others

• [USER] Updated golang version to v1.19.2 (gardener/machine-controller-manager#753, @rishabh-11)
• [USER] If during a rolling update scale-up is done, MCM scales up only the new machineSet, while in case of scale-down the scale-down amount is split among all active machineSets (.i.e. with .spec.replicas> 0), in proportion to their sizes. (gardener/machine-controller-manager#765, @himanshu-kun)
• [DEVELOPER] go version updated to 1.19.4 in pipeline and Dockerfile (gardener/machine-controller-manager#766, @himanshu-kun)

v0.47.0

[machine-controller-manager]

✨ New Features

• [USER] Bootstrap token replacement by MCM is now supported for Ignition userData format (gardener/machine-controller-manager#743, @Gerrit91)

🐛 Bug Fixes

• [OPERATOR] resourceName machine-controller added for leases in clusterrole. Updated version of Clusterroles and Clusterrolebindings to v1. (gardener/machine-controller-manager#738, @rishabh-11)

🏃 Others

• [OPERATOR] Migrated clients to use policy/v1 PodDisruptionBudget for kubernetes versions >= 1.21. policy/v1beta1 PDB is also supported but for k8s < 1.21 (gardener/machine-controller-manager#744, @shafeeqes)

v0.46.1

[machine-controller-manager]

🐛 Bug Fixes

• [OPERATOR] resourceName machine-controller added for leases in clusterrole. Updated version of Clusterroles and Clusterrolebindings to v1. (gardener/machine-controller-manager#739, @rishabh-11)

v0.46.0

[machine-controller-manager]

⚠️ Breaking Changes

• [OPERATOR] The default leader election resource lock of machine-controller-manager has been changed from endpointsleases to leases. (gardener/machine-controller-manager#711, @acumino)
  • Please make sure, that you had at least machine-controller-manager@v0.43.0 running before upgrading to v0.46.0, so that it has successfully acquired leadership with the hybrid resource lock (endpointsleases) at least once.

🐛 Bug Fixes

• [USER] Rollout freeze won't happen due to Unknown machines now. (gardener/machine-controller-manager#733, @himanshu-kun)

🏃 Others

• [OPERATOR] Published docker images for Machine-Controller-Manager are now multi-arch ready. They support linux/amd64 and linux/arm64. (gardener/machine-controller-manager#732, @timuthy)
• [OPERATOR] The machine-controller-manager container now uses distroless instead of alpine as a base image. (gardener/machine-controller-manager#734, @dimityrmirchev)

v0.45.0

[machine-controller-manager]

📖 Documentation

• [USER] upgraded k8s dependecy to v1.22.9 (revendor in providers required to see effects) (gardener/machine-controller-manager#721, @Mkmittal)
• [DEPENDENCY] Paths transformations in .docforge/manifest.yaml for simplification (gardener/machine-controller-manager#689, @Kostov6)

🏃 Others

• [OPERATOR] Base image updated to alpine v3.15.4 and build image to golang 1.17.9. (gardener/machine-controller-manager#713, @himanshu-kun)
• [DEPENDENCY] K8s dependency upgraded to 1.21.12 (gardener/machine-controller-manager#719, @Mkmittal)

v0.44.2

no release notes available

v0.44.1

no release notes available

v0.44.0

[machine-controller-manager]

🐛 Bug Fixes

• [USER] The value for key cluster-autoscaler.kubernetes.io/scale-down-disabled placed by MCM is now true and not True. This typo stopped MCM from disabling CA from scaling down during rolling update. (gardener/machine-controller-manager#685, @himanshu-kun)
• [USER] MCM now marks 1 machine per machineDeployment as Failed at a time in case of healthTimeout. This is introduced to deal with meltdown scenario (gardener/machine-controller-manager#683, @himanshu-kun)

🏃 Others

• [OPERATOR] machine-controller-manager does now log the Node conditions when it considers Machine as unhealthy (and changes its state to Unknown). (gardener/machine-controller-manager#676, @ialidzhikov)

v0.43.1

[machine-controller-manager]

🐛 Bug Fixes

• [USER] typo stopping scaleDown disabling during cluster rollout is fixed (gardener/machine-controller-manager#687, @himanshu-kun)

v0.43.0

[machine-controller-manager]

⚠️ Breaking Changes

• [OPERATOR] Components that deploy the machine-controller-manager will now have to adapt the RBAC rules to allow machine-controller-manager to maintain its leader election resource lock in leases as well. (gardener/machine-controller-manager#662, @acumino)

✨ New Features

• [OPERATOR] orphan collection is also triggered if machine obj is updated with having multiple backing VMs (gardener/machine-controller-manager#667, @himanshu-kun)

🏃 Others

• [USER] Updated golang version to v1.17 (gardener/machine-controller-manager#664, @AxiomSamarth)
• [OPERATOR] The default leader election resource lock of machine-controller-manager has been changed from endpoints to endpointsleases. (gardener/machine-controller-manager#662, @acumino)