v0.23.0

no release notes available

v0.22.0

[machine-controller-manager]

🐛 Bug Fixes

• [USER] Fix a bug in the bootstrap token creation that caused node to not be able to join the cluster due to an expired bootstrap token. (gardener/machine-controller-manager#777, @himanshu-kun)
• [USER] An edge case where all the machineSets were scaled down to zero has been dealt with. (gardener/machine-controller-manager#804, @himanshu-kun)

v0.21.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [OPERATOR] CVE categorization for mcm-provider-vsphere has been added. (gardener/machine-controller-manager-provider-vsphere#52, @dkistner)

v0.20.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [OPERATOR] Update machine-controller-manager-provider-vsphere Golang to 1.19.5 (gardener/machine-controller-manager-provider-vsphere#49, @briantopping)

[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 old machineSets, 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.19.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [USER] Upgrade golang to 1.19.4 (gardener/machine-controller-manager-provider-vsphere#46, @briantopping)

v0.18.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [OPERATOR] Upgraded individual library dependencies for executables (gardener/machine-controller-manager-provider-vsphere#44, @briantopping)

v0.17.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#739, @rishabh-11)
• [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.16.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [OPERATOR] support most recent flatcar versions (gardener/machine-controller-manager-provider-vsphere#40, @christianhuening)
  • build with golang 1.18.4

[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.15.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [OPERATOR] Use distroless as base image (gardener/machine-controller-manager-provider-vsphere#34, @MartinWeindel)

v0.14.0

[machine-controller-manager-provider-vsphere]

🏃 Others

• [DEVELOPER] Update govmomi code to v0.28.0 (gardener/machine-controller-manager-provider-vsphere#31, @tuxgoose)

📰 Noteworthy

• [OPERATOR] upgraded to mcm version 0.45.0 (gardener/machine-controller-manager-provider-vsphere#32, @rfranzke)