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 [email protected] 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)

v0.42.0

[machine-controller-manager]

✨ New Features

• [USER] End User can now delete the backing machine object of the node instantly by annotating the desired node with 'node.machine.sapcloud.io/trigger-deletion-by-mcm="true"` (gardener/machine-controller-manager#648, @AxiomSamarth)

v0.41.0

[machine-controller-manager]

✨ New Features

• [USER] Added *expectedNodeDetails field to the MachineClass API (#644, @AxiomSamarth)

🐛 Bug Fixes

• [OPERATOR] A bug has been fixed in the pre-delivered CRD manifests for MCM (/kubernetes/crds). It caused data to be pruned from MCM related resources and led to reconciliation issues. (#641, @timuthy)

📖 Documentation

• [DEVELOPER] make generate now generates v1 version of CRDs by default instead of v1beta1. (#640, @himanshu-kun)

🏃 Others

• [USER] Update Kubernetes dependency versions to v1.20.6 (#601, @AxiomSamarth)

v0.40.0

[machine-controller-manager]

⚠️ Breaking Changes

• [OPERATOR] Draining of pods with PVs (Persistent Volume) now waits for re-attachment of PV on a different node when volumeAttachments support is enabled on the cluster. Else it falls back to the default PV reattachment timeout value configured. The default value is 90s and this can be overwritten via the machine-pv-reattach-timeout flag. Please enable permissions to allow listing of volumeAttachments resource while importing these changes. (#608, @prashanth26)

✨ New Features

• [USER] Increase default concurrent object syncs to 50 to allow more concurrent reconciles to occur. (#629, @prashanth26)
• [USER] Machine rollouts are now more as desired with the number of replicas always maintained to desired + maxSurge. Earlier machines in termination were left out of this calculation but now is considered with this change. (#627, @prashanth26)
• [OPERATOR] Finalizers will be added to the MachineClass which is used by at least one machine. Machines whose backing MachineClass does not have finalizers shall not be reconciled. (#593, @AxiomSamarth)
• [DEVELOPER] Replace integration test with unit test to test the functionality to freeze MachineSet (#620, @AxiomSamarth)

🐛 Bug Fixes

• [OPERATOR] Avoids blocking of drain call when the buffer is full for the volumeAttachmentHandlers. (#627, @prashanth26)
• [DEVELOPER] Test framework now fetches secrets from the correct (control) APIServer while running tests. (#617, @himanshu-kun)

🏃 Others

• [OPERATOR] Nodes attached to the cluster without MCM support are now annotated with "node.machine.sapcloud.io/notManagedByMCM": "1". This is then ignored by the MCM for further processing. (#612, @himanshu-kun)