Update machine-controller-manager to v0.60.0 (minor) #12842
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.59.2
->v0.60.0
v0.59.2
->v0.60.0
Release Notes
gardener/machine-controller-manager (gardener/machine-controller-manager)
v0.60.0
Compare Source
[github.com/gardener/machine-controller-manager:v0.60.0]
✨ New Features
[OPERATOR]
When running without a target cluster machine-controller-manager will report a new status fieldaddresses
by @maboehm [#1012][OPERATOR]
Machine Class now has VirtualCapacity field hat maps to WorkerPool's NodeTemplate VirtualCapacity. by @elankath [#1024]🐛 Bug Fixes
[OPERATOR]
Fixed metricmcm_machine_set_failed_machines
and underlying variable*machineSet.Status.FailedMachines
so that they reflect the current state of machines by @gagan16k [#1025][USER]
Fixed checking ofcreateMachineTimeout
when machine isPending
by @thiyyakat [#1015][OPERATOR]
Fixed a bug where machines in theInPlaceUpdating
phase were incorrectly transferred to the new machine set during inplace updates. This caused the machine controller to miss updating the phase toInPlaceUpdateSuccessful
, resulting in machines getting stuck or marked asInPlaceUpdateFailed
. by @acumino [#1020]🏃 Others
[OPERATOR]
node.gardener.cloud/critical-components-not-ready
taint is added to the node after the successful in-place update to prevent scheduling any workload before critical component pods are ready. by @acumino [#1017][OPERATOR]
export testresults as inlined ocm-resource by @heldkat [#1022][DEVELOPER]
migrate CICD-Pipeline to GitHub-Actions by @ccwienk [#1011][OPERATOR]
Add informational logging for MachineDeployment rollout events by @gagan16k [#1029][DEVELOPER]
Convert.reuse/dep5
toREUSE.toml
. by @thiyyakat [#1026]Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
Release note: