v0.39.0

[machine-controller-manager]

✨ New Features

• [USER] Skip node drain on ReadOnlyFileSystem condition (#605, @himanshu-kun)
• [OPERATOR] Improved log details to include node name and provider-ID in addition to existing machine name (#607, @himanshu-kun)

🐛 Bug Fixes

• [OPERATOR] Fix panic when machineClass secretRef isn't found. (#609, @jsravn)
• [DEVELOPER] Adds finalizers on machines that are adopted by the machine controller. Without this change, it causes issues while migrating machine objects between clusters. (#611, @prashanth26)

v0.38.0

[machine-controller-manager]

🐛 Bug Fixes

• [DEVELOPER] Azure: Improved NIC creation and deletion logic to handle NIC creation and deletions more gracefully. (#594, @prashanth26)

v0.37.0

[machine-controller-manager]

⚠️ Breaking Changes

• [DEVELOPER] machine-controller-manager now checks for misconfigured PodDisruptionBudgets (ones that require zero voluntary evictions and make impossible the graceful Node drain) and sets better Machine .status.lastOperation.description for such Machines. This change is breaking as out-of-tree providers need new RBAC permissions - list and watch access for PodDisruptionBudgets in the target cluster. (#591, @ialidzhikov)

🏃 Others

• [OPERATOR] Avoid the deletion of the machines in CrashLoopBackoff state by the safety controller (#589, @AxiomSamarth)

v0.36.0

[machine-controller-manager]

✨ New Features

• [OPERATOR] All machine classes do now support an optional .{spec.}credentialsSecretRef field in addition to today's .{spec.}secretRef field. If .{spec.}credentialsSecretRef is non-nil then the provider credentials will be read out of this secret. The user-data for the machine bring-up is still required to be part of the secret referenced by .{spec.}secretRef. (#578, @rfranzke)
• [OPERATOR] Some machine class secrets are now supporting alternative data keys: (#578, @rfranzke)
  • The machine class secret for Alicloud machines does now also accept the data keys accessKeyID and accessKeySecret as alternatives for today's keys.
  • The machine class secret for AWS machines does now also accept the data keys accessKeyID and secretAccessKey as alternatives for today's keys.
  • The machine class secret for Azure machines does now also accept the data keys clientID, clientSecret, subscriptionID and tenantID as alternatives for today's keys.
  • The machine class secret for GCP machines does now also accept the data key serviceaccount.json as alternatives for today's key.

🏃 Others

• [OPERATOR] Bumped AWS SDK version to v1.23.13 (#580, @zjj2wry)
• [OPERATOR] An issue causing panic when the encoded machine template hash length is less than expect limit is now fixed. (#575, @ialidzhikov)
• [OPERATOR] MCM will delete Azure machines even if the underlying resource group is already deleted. (#566, @dkistner)
• [OPERATOR] Set Machine Phase to Terminating before draining. (#564, @prashanth26)
• [DEVELOPER] Update docker images to use gcr copy (#574, @prashanth26)
• [DEVELOPER] Update docker image versions to golang:1.15.5 & alpine:3.12.1 (#574, @prashanth26)

📰 Noteworthy

• [OPERATOR] Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp. (#564, @prashanth26)

v0.35.2

[machine-controller-manager]

Improvements

• [OPERATOR] An issue causing panic when the encoded machine template hash length is less than expect limit is now fixed. (#575, @AxiomSamarth)

v0.35.1

[machine-controller-manager]

Most notable changes

• [OPERATOR] Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp.. (#564, @prashanth26)

Improvements

• [OPERATOR] Set Machine Phase to Terminating before draining. (#564, @prashanth26)

v0.34.4

[machine-controller-manager]

Most notable changes

• [OPERATOR] Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp. (#564, @prashanth26)

Improvements

• [OPERATOR] Set Machine Phase to Terminating before draining. (#564, @prashanth26)

v0.35.0

[machine-controller-manager]

Most notable changes

• [USER] NetworkUnavailable node condition is also considered by default while considering the machine's to be unhealthy. (#543, @rewiko)
• [USER] AWS: Allows deletion of machines even on modify instance call failure (#515, @prashanth26)
• [OPERATOR] OOT: Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (#557, @prashanth26)
• [OPERATOR] Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (#525, @hardikdr)

Improvements

• [USER] The default drainTimeout value has been updated from 12hours to 2hours. (#554, @prashanth26)
• [USER] OOT: Fixed regression with maxEvictRetries (#554, @prashanth26)
• [USER] Adds the ability to specify an already existing OpenStack Neutron network in the subnetID of an OpenStackMachineClass. MCM will deploy new machines into the given subnet by pre-allocating Neutron ports and pass them to the Nova server object. (#545, @MrBatschner)
• [USER] The machine-controller-manager supports now machines attached to Azure VirtualMachineScaleSet Orchestration Mode VM (VMO). (#519, @dkistner)
• [USER] Restored tag verification in the Azure driver to filter VMs/disks/NICs based on tags (#507, @zuzzas)
• [OPERATOR] Allow migration to continue when ProviderMachineClass is missing but MachineClass with the same name as ProviderMachineClass is found. Updates Machine object references to the MachineClass. (#559, @prashanth26)
• [OPERATOR] Use cache-based listers to GET the machine-object while reconciling. (#558, @hardikdr)
• [OPERATOR] OOT: Enqueue machine only when node conditions have changed. (#557, @prashanth26)
• [OPERATOR] Adapted integration tests to handle possibly orphaned resources. (#550, @hardikdr)
• [OPERATOR] OOT: Fixes drain timeout issues on retires (#548, @prashanth26)
• [OPERATOR] NetworkUnavailable nodeCondition added to the example, some CNI will update this condition depending on the state of the CNI or the network availability. (#543, @rewiko)
• [OPERATOR] Added a more comprehensive set of events to trigger machine class reconciliations. (#531, @prashanth26)
• [OPERATOR] Finalizers are added by default for all machine class objects. (#531, @prashanth26)
• [OPERATOR] Bootstrap token injection now works in the new OOT Machine controller (#521, @zuzzas)
• [OPERATOR] Add support for ServerGroups in the Openstack driver. VMs can now be created in the ServerGroup specified in the respective MachineClass. (#511, @kon-angelo)
• [OPERATOR] Bugfix: Consider CSI PersistentVolumes during the eviction of Pods with PersistentVolumes. (#509, @ialidzhikov)
• [DEVELOPER] Adds a new phase CrashLoopBackOff that is set due to machine creation failures. (#525, @hardikdr)
• [DEVELOPER] The field availabilitySets in the AzureMachineClass is now deprecated in favour of the field machineSet, which allow to configure AvailabilitySets and VirtualMachineScaleSet Orchestration Mode VM (VMO). The field will be removed in the future. (#519, @dkistner)

v0.34.3

[machine-controller-manager]

Improvements

• [OPERATOR] Added a more comprehensive set of events to trigger machine class reconciliations. (#532, @prashanth26)
• [OPERATOR] Finalizers are added by default for all machine class objects. (#532, @prashanth26)

v0.34.2

[machine-controller-manager]

Most notable changes

• [OPERATOR] Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (#523, @hardikdr)

Improvements

• [DEVELOPER] Adds a new phase CrashLoopBackOff that is set due to machine creation failures. (#523, @hardikdr)