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)

v0.33.2

[machine-controller-manager]

Most notable changes

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

Improvements

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

v0.34.1

[machine-controller-manager]

Improvements

• [OPERATOR] AWS: Allow deletion of VMs even on list image or modify instance failure (#516, @prashanth26)

v0.33.1

[machine-controller-manager]

Most notable changes

• [USER] Allow deletion of VM even on image/instance get failures. (#520, @prashanth26)

v0.34.0

[machine-controller-manager]

Most notable changes

• [USER] Support for Spot Instances is available in AWS driver. If the spotPrice is empty, price is automatically set to the on-demand price so that Spot instance can launch immediately. (#481, @zuzzas)
• [OPERATOR] RBAC policies have to be updated to allow updating of node/status resources. (#492, @guydaichs)
• [OPERATOR] New flag delete-migrated-machine-class is introduced. When set to true (defaulted to false), deletes any provider-specific machine class (e.g. AWSMachineClass) that has the machine.sapcloud.io/migrated annotation set on it. (#484, @prashanth26)
• [DEVELOPER] Added migration logic for moving from provider-specific machine class to generic machine classes in out of tree code path. On migration, the machine.sapcloud.io/migrated annotation set on the old machine class. (#484, @prashanth26)
• [DEVELOPER] The machine controller adds finalizer only when machine reference is present, deletes it otherwise. (#484, @prashanth26)

Improvements

• [USER] Retry when secret is referred by machineClass is missing (#495, @AxiomSamarth)
• [USER] Node condition is added to the status of terminating nodes indicating the termination start time and reason (Unhealthy|ScaleDown) (#492, @guydaichs)
• [OPERATOR] All nodes under machine deployments being rolled-out are annotated with cluster-autoscaler.kubernetes.io/scale-down-disabled: "True" during the period of rolling-update. (#496, @hardikdr)
• [OPERATOR] A new command line flag autoscaler-scaldown-annotation-during-rollout is introduced to disable annotating the nodes with cluster-autoscaler annotation cluster-autoscaler.kubernetes.io/scale-down-disabled during rollout. (#496, @hardikdr)

v0.33.0

[machine-controller-manager]

Improvements

• [OPERATOR] Avoids race between secret finalizer creation/deletion between in-tree & OOT controllers (#487, @prashanth26)
• [OPERATOR] Enable finer machine configurations per MachineDeployment/MachineSet/Machines basis. Exposed configurations: MachineDrainTimeout, MachinHealthTimeout, MachineCreationTimeout, MaxEvictRetries, NodeConditions. (#478, @hardikdr)
• [DEVELOPER] Increased default concurrent worker syncs from 5 --> 10 (#491, @prashanth26)

v0.32.0

[machine-controller-manager]

Improvements

• [OPERATOR] Added an option to use configDrive in the OpenStackMachineClass (#457, @zuzzas)
• [DEVELOPER] Bugfix: Drain machines with only a valid node (name) (#480, @prashanth26)

v0.31.0

[machine-controller-manager]

Improvements

• [OPERATOR] Azure: Fixes regression when using a VM image resource id instead of an URN (for example an image from a shared image gallery) (#475, @MSSedusch)
• [OPERATOR] CRDs are now generated with full OpenAPI schema. (#471, @mvladev)