Hardik Dodiya
Hardik Dodiya
**What would you like to be added**: Currently, MCM boots-up the machines with only one root disk, we should allow users to be able to attach multiple worker-disks. There has...
**What would you like to be added**: On failure of machine creation or deletion requests, MCM constantly tries to create or delete the machine-objects. This could cause a heavy load...
**What would you like to be added**: In order to test MCM independent of Gardener, the created machines has to join the cluster. And this requires the machine to be...
## Improvement Currently MCM stores node-object name at both `labels` and `Status.Node` on machine-object. We can remove the dependency from the `Status.Node`, and use only labels. This could be helpful...
**What would you like to be added**: During rolling-updates, we decrease the replicas of the old-machine-set and gradually increase the ones in the new-machine-set respecting `maxSurge`/`maxUnavailable`. Currently, when the newer...
**What would you like to be added**: MCM has been computing the name of the machine-resources so far, it would probably be a good idea to use the `generateName` feature,...
**How to categorize this issue?** /area usability /kind enhancement /priority normal /platform aws **What would you like to be added**: The extension allows users to configure multiple volumes/disks to the...
# Summary This is to propose the Kubernetes-node style health-check mechanisms for the MachinePools. It shall circumvent the issues related to degraded health of the previously `Ready` MachinePools. The possible...
# Summary This issue aims to enable extensible and policy-rich scheduling for VirtualMachines and MetalMachines in the onmetal-api. The proposed approach is to introduce the capability to plug-in and plug-out...