Madhav Bhargava

>If we follow the constraints strictly, we should rather not make the kube-apiserver Service topology-aware. WDYT? This is a documented limitation and also points to just one case where a...

> **I would argue that all clusters with nodes have at least one zone ;-) .** > Whether or not the provider calls it "zone", the machines need to run...

> Today workers is a slice of worker objects. It won't be possible to add zoneConfigurations directly to workers What we (Vedran with the MCM team where this proposal was...

** MOM (16 March )** Attendees: @dkistner, @himanshu-kun , @dguendisch, @unmarshall The requirement and the need for it was discussed which is now captured as part of this ticket (see...

**MOM** -------------------------------------------------------------------------- **Attendees:** @himanshu-kun , @rishabh-11 , @elankath , @unmarshall MCServer today allows configuration of [machine-creation-timeout](https://github.com/gardener/machine-controller-manager/blob/master/pkg/util/provider/app/options/options.go#L67) but does not have a corresponding `machine-deletion-timeout`. We need a way to determine when...

We must observe if `force deletion of VM` is required since we no longer detach the disks first but instead leverage cascade delete. So forceful deletion of the VMs is...

We (me and @himanshu-kun) noticed at least in azure, that there is no use case for force deletion of the VM whose `ProvisioningState` is set to `Failed`. A simple VM...

We should just add a doc that the default value is set to 0. There are 2 different recommendations: 1. If MCM is used standalone without using CA then consumers...

> but this has the drawback of not being able to name for the case when MC is running locally as a process. You can pass a command line flag....

Yes hostname should serve as long as you are going to start a single process locally. If you wish to start more than one process locally then that will again...