v0.12.0
·
85 commits
to master
since this release
[machine-controller-manager-provider-aws]
🏃 Others
- [OPERATOR] machine-controller-manager-provider-aws now uses
distroless
instead ofalpine
as a base image. (gardener/machine-controller-manager-provider-aws#90, @ialidzhikov) - [DEVELOPER] probeResources() now doesn't try to delete orphan resources but only lists them. (gardener/machine-controller-manager-provider-aws#85, @Mkmittal)
- The beforeSuite for IT test now calls for cleanup of orphan resources separately.
- The Integration Test, which looks for orphan resources, now doesn't try to delete the orphan resources and just waits for them to be done automatically.
[machine-controller-manager]
⚠️ Breaking Changes
- [OPERATOR] The default leader election resource lock of
machine-controller-manager
has been changed fromendpointsleases
toleases
. (gardener/machine-controller-manager#711, @acumino)- Please make sure, that you had at least
machine-controller-manager@v0.43.0
running before upgrading tov0.46.0
, so that it has successfully acquired leadership with the hybrid resource lock (endpointsleases
) at least once.
- Please make sure, that you had at least
🐛 Bug Fixes
- [USER] Rollout freeze won't happen due to
Unknown
machines now. (gardener/machine-controller-manager#733, @himanshu-kun)
🏃 Others
- [OPERATOR] Published docker images for Machine-Controller-Manager are now multi-arch ready. They support
linux/amd64
andlinux/arm64
. (gardener/machine-controller-manager#732, @timuthy) - [OPERATOR] The
machine-controller-manager
container now usesdistroless
instead ofalpine
as a base image. (gardener/machine-controller-manager#734, @dimityrmirchev)