NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #3125 by repository stars
Latest stable
v0.63.1
Last release 11 days ago
11 Nov 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
287 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
*[USER]* Added *expectedNodeDetails field to the MachineClass API (#644, @AxiomSamarth)
/kubernetes/crds). It caused data to be pruned from MCM related resources and led to reconciliation issues. (#641, @timuthy)make generate now generates v1 version of CRDs by default instead of v1beta1. (#640, @himanshu-kun)Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
*[OPERATOR]* Draining of pods with PVs (Persistent Volume) now waits for re-attachment of PV on a different node when volumeAttachments support is ena
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)desired + maxSurge. Earlier machines in termination were left out of this calculation but now is considered with this change. (#627, @prashanth26)"node.machine.sapcloud.io/notManagedByMCM": "1". This is then ignored by the MCM for further processing. (#612, @himanshu-kun)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
*[USER]* Skip node drain on ReadOnlyFileSystem condition (#605, @himanshu-kun)
secretRef isn't found. (#609, @jsravn)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
*[DEVELOPER]* Azure: Improved NIC creation and deletion logic to handle NIC creation and deletions more gracefully. (#594, @prashanth26)
Nothing published for this version
*[DEVELOPER]* machine-controller-manager now checks for misconfigured PodDisruptionBudgets (ones that require zero voluntary evictions and make imposs
.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)*[OPERATOR]* All machine classes do now support an optional .{spec.}credentialsSecretRef field in addition to today's .{spec.}secretRef field. If .{sp
.{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)accessKeyID and accessKeySecret as alternatives for today's keys.accessKeyID and secretAccessKey as alternatives for today's keys.clientID, clientSecret, subscriptionID and tenantID as alternatives for today's keys.serviceaccount.json as alternatives for today's key.golang:1.15.5 & alpine:3.12.1 (#574, @prashanth26)*[OPERATOR]* An issue causing panic when the encoded machine template hash length is less than expect limit is now fixed. (#575, @AxiomSamarth)
*[OPERATOR]* Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp.. (#564, @prashanth26)
*[DEVELOPER]* The field availabilitySets in the AzureMachineClass is now deprecated in favour of the field machineSet, which allow to configure Availa…
MachineClass. (#511, @kon-angelo)CrashLoopBackOff that is set due to machine creation failures. (#525, @hardikdr)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)*[OPERATOR]* Machine force deletion computation is based on deletionTimestamp instead of LastUpdatedTimestamp. (#564, @prashanth26)
*[OPERATOR]* Added a more comprehensive set of events to trigger machine class reconciliations. (#532, @prashanth26)
Nothing published for this version
*[OPERATOR]* Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (#523, @hardik
CrashLoopBackOff that is set due to machine creation failures. (#523, @hardikdr)*[OPERATOR]* AWS: Allow deletion of VMs even on list image or modify instance failure (#516, @prashanth26)
Nothing published for this version
Nothing published for this version
*[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 S
spotPrice is empty, price is automatically set to the on-demand price so that Spot instance can launch immediately. (#481, @zuzzas)node/status resources. (#492, @guydaichs)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)cluster-autoscaler.kubernetes.io/scale-down-disabled: "True" during the period of rolling-update. (#496, @hardikdr)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)*[OPERATOR]* Introduced a backoff in re-enqueuing machines on creation/deletion failures. Avoids throttling APIServer & provider calls. (#527, @prasha
CrashLoopBackOff that is set due to machine creation failures. (#527, @prashanth26)*[USER]* Allow deletion of VM even on image/instance get failures. (#520, @prashanth26)
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
*[OPERATOR]* Avoids race between secret finalizer creation/deletion between in-tree & OOT controllers (#487, @prashanth26)
Nothing published for this version
*[OPERATOR]* Added an option to use configDrive in the OpenStackMachineClass (#457, @zuzzas)
*[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, @MS
*[DEVELOPER]* Support for external / OOT (Out Of Tree) machine controller. A new provider can be maintained out of the core MCM repository. (#460, @pr
*[USER]* Azure: Add support for custom image plans for VMs (#463, @MSSedusch)
*[USER]* Provide a way to specify "auth-extra-groups" field in created bootstrap tokens. (#442, @zuzzas)
*[OPERATOR]* Prepend mcm to all work queue metrics (#420, @prashanth26)
Status.Node is not set. (#432, @hardikdr)*[OPERATOR]* Set deleteOnTermination flag to true while deleting the VMs in AWS. (#409, @prashanth26)
*[OPERATOR]* Bugfix: Set deleteOnTermination to true by default for volumes. Disks that are created with the instance are deleted with instance termin
*[OPERATOR]* Prepend mcm to all work queue metrics (#405, @prashanth26)
Nothing published for this version
*[USER]* Updated dependecies to refer k8s 1.16.0 (#401, @prashanth26)
github.com/Azure/azure-sdk-for-go is updated to v32.6.0. (#369, @ialidzhikov)One column per quarter.