0.21.0

[machine-controller-manager]

Most notable changes

• [USER] Fixes issues while draining nodes in unknown state. (#320, @prashanth26)
• [OPERATOR] Fixes consistency issues with machine-deployments, machine-classes, and secrets. (#319, @hardikdr)

Improvements

• [USER] Fixes issues while overriding termination grace periods for pods with larger values. (#320, @prashanth26)
• [USER] Deletes nodes object on machine (object) deletion (#316, @prashanth26)
• [OPERATOR] Better error handling while adding/removing the finalizers on machine classes & secrets. (#319, @hardikdr)
• [OPERATOR] Re-enqueues the machine classes and secrets periodically(~10mins). (#319, @hardikdr)
• [OPERATOR] Bugfix: Eliminates creation of orphan NICs when VM creation fails on Azure (#313, @prashanth26)
• [OPERATOR] Added additional OpenStack credentials for DomainID, TenantID, UserDomainName (#311, @afritzler)
• [OPERATOR] Bugfix: Allows force deletion of pods who have no controllers backing them (#300, @prashanth26)

0.20.1

[machine-controller-manager]

Improvements

• [OPERATOR] Bugfix: Allows force deletion of pods who have no controllers backing them (#301, @prashanth26)

0.20.0

[machine-controller-manager]

Most notable changes

• [USER] MCM now needs permissions to GET/LIST PV and PVCs on target cluster while draining machines (#275, @ggaurav10)
• [OPERATOR] Changes the drain logic to honour the individual pods' terminationGracePeriodSeconds instead of a fixed(though configurable) timeout. For the pods without volumes, the timeout would be a bit longer than the maximum of terminationGracePeriodSeconds of the pods without volume. For the pods with volumes, the timeout is its own terminationGracePeriodSeconds and a fixed (but configurable) volume detach timeout for each pod. (#288, @amshuman-kr)
  • The command-line flags machine-max-evict-retries and machine-pv-detach-timeout can be used to customize the default behaviour of the number of retries for eviction and wait period for the detaching of volumes after pods are evicted/deleted.
  • The default value for the existing command-line flag machine-drain-timeout has been increased to 12h which should be enough for most work-loads.

Improvements

• [OPERATOR] Increased OpenStack server status wait for a timeout during server creation from 5 to 10 mins. (#286, @kayrus)
• [OPERATOR] Improved the server status handling - It no longer waits for the timeout if the server status is different from BUILD during server creation. (#286, @kayrus)
• [OPERATOR] Force deletion of machine succeeds even on drain failures (#283, @prashanth26)
• [OPERATOR] dep is replaced by go mod. (#280, @ialidzhikov)
• [OPERATOR] When draining a node, pods with PVCs are evicted serially. Next pod eviction waits for PV of the previously evicted pod to detach from the node. Operators can expect faster machine drains for their machines. (#275, @ggaurav10)

0.19.0

[machine-controller-manager]

Most notable changes

• [USER] Orphan VMs/disks/NICs handler has been fixed (#261, @prashanth26)
• [OPERATOR] Update Azure SDK from 12.5-beta to 26.1 (#261, @prashanth26)

Improvements

• [OPERATOR] Fix panic in AWS driver if AMI not found. (#279, @amshuman-kr)
• [OPERATOR] Fixes packet driver (#273, @deitch)
• [OPERATOR] Ensure 'x-ms-request-id' header is logged in case of Azure API failures. (#261, @prashanth26)

0.18.0

[machine-controller-manager]

Most notable changes

• [USER] Deletion of annotations, labels and taints are now supported (#268, @prashanth26)

Improvements

• [OPERATOR] The machine-controller-manager does now correctly add its finalizer to Alicloud machine class secrets. (#271, @rfranzke)
• [OPERATOR] Multiple taints with the same key but different values are now supported (#268, @prashanth26)

0.17.0

[machine-controller-manager]

Most notable changes

• [USER] Enables support for propagating and maintaining the taints, annotations and labels from machine-api objects to node-objects. (#256, @hardikdr)

Improvements

• [OPERATOR] Bugfix: Existing machine-objects now adopts the node-label. (#265, @hardikdr)
• [OPERATOR] Bugfix: MachineDeployment with partial freeze status has been syncronized to display the correct status (#264, @prashanth26)
• [OPERATOR] Added safety controller cases in integration tests (#257, @prashanth26)

0.16.0

[machine-controller-manager]

Most notable changes

• [USER] Manual unfreezing of machineSets and machineDeployment is now possible using the annotation - 'safety.machine.sapcloud.io/unfreeze': 'True' (#253, @prashanth26)
• [USER] The drain is always invoked even the case of forceful deletion (#248, @prashanth26)
• [USER] Drain now tries to evict pods and if eviction fails, it forcefully deletes the pods (#248, @prashanth26)

Improvements

• [OPERATOR] Bugfix: Improvements while unfreezing machineSet/machineDeployment (#251, @prashanth26)
• [OPERATOR] Drain logic makes use of lesser API calls (#249, @hardikdr)
• [OPERATOR] Azure explicitly detaches data disks before VM deletion (#248, @prashanth26)
• [OPERATOR] Enhanced unit-test coverage for machineset controller (#241, @hardikdr)
• [OPERATOR] The golang version has been upgraded to v1.12.0. (#237, @ialidzhikov)

0.15.0

[machine-controller-manager]

Improvements

• [OPERATOR] AliCloud driver now generates the correct ProviderID on machine-object. (#236, @prashanth26)
• [OPERATOR] Bug fixed in machineSet unfreeze logic (#239 , @prashanth26)

0.14.0

[machine-controller-manager]

Improvements

• [OPERATOR] Removes null pointer exception on Azure (#232, @prashanth26)
• [OPERATOR] Machine CRDs now use status subresource (#228, @prashanth26)

0.13.0

[machine-controller-manager]

Improvements

• [OPERATOR] Fixes panic issue while fetching metrics of failed machines (#225, @prashanth26)