v0.14.0
gardener-robot-ci-2
released this
26 May 07:21
·
47 commits
to master
since this release
[machine-controller-manager-provider-openstack]
⚠️ Breaking Changes
- [OPERATOR] Support for migration of machineClass is dropped by the mcm-provider (gardener/machine-controller-manager-provider-openstack#89, @kon-angelo)
🏃 Others
- [USER] Updated golang version to v1.19.4 (gardener/machine-controller-manager-provider-openstack#75, @rishabh-11)
- [USER] Update golang to
v1.20.4
(gardener/machine-controller-manager-provider-openstack#90, @kon-angelo) - [OPERATOR] CVE categorization for mcm-provider-openstack has been added. (gardener/machine-controller-manager-provider-openstack#81, @dkistner)
- [DEPENDENCY] Revendor gardener to
v1.69.3
(gardener/machine-controller-manager-provider-openstack#89, @kon-angelo) - [DEPENDENCY] Revendor MCM to
v0.49.0
(gardener/machine-controller-manager-provider-openstack#89, @kon-angelo) - [DEPENDENCY] upgraded dependency: (gardener/machine-controller-manager-provider-openstack#92, @himanshu-kun)
- github.com/gardener/machine-controller-manager -> v0.49.1
[machine-controller-manager]
⚠️ Breaking Changes
- [USER]
node
field is removed from machine status. controller will now depend on the node label which already was present in the machine object's metadata. If you(or your controller) are dependent on thestatus.node
field of the machine object, then kindly usenode
label under.metadata.labels
(gardener/machine-controller-manager#745, @rishabh-11)
✨ New Features
- [USER] MachineDeployment would now have
Progressing
condition even when no progress Deadline is specified. This condition would never go to the reasonProgressDeadlineExceeded
in that case. (gardener/machine-controller-manager#762, @himanshu-kun) - [OPERATOR] Using
kubectl get machines
will displayNode
of the corresponding machine as a column. If-owide
flag is used then the correspondingProviderID
will also be displayed. (gardener/machine-controller-manager#746, @rishabh-11) - [OPERATOR] Added new short names for machine(mc), machineClass(mcc), machineDeployment(mcd), and machineSet(mcs) resources. (gardener/machine-controller-manager#749, @rishabh-11)
🐛 Bug Fixes
- [USER] Fix a bug in the bootstrap token creation that caused node to not be able to join the cluster due to an expired bootstrap token. (gardener/machine-controller-manager#777, @himanshu-kun)
- [USER] An edge case where all the machineSets were scaled down to zero has been dealt with. (gardener/machine-controller-manager#804, @himanshu-kun)
🏃 Others
- [USER] Updated golang version to v1.19.2 (gardener/machine-controller-manager#753, @rishabh-11)
- [USER] If during a rolling update scale-up is done, MCM scales up only the new machineSet, while in case of scale-down the scale-down amount is split among old machineSets, in proportion to their sizes. (gardener/machine-controller-manager#765, @himanshu-kun)
- [DEVELOPER] go version updated to 1.19.4 in pipeline and Dockerfile (gardener/machine-controller-manager#766, @himanshu-kun)