Hardik Dodiya
Hardik Dodiya
@zuzzas Did you prepare any sample cloud-config during your tests back then, which could be used here in documentation? :)
We do link check here: https://github.com/gardener/machine-controller-manager/blob/master/.ci/check#L61 , in case it helps. Also, what version of MCM were you rebasing/using?
GKE enabled support for Pre-emptible VMs: https://cloud.google.com/kubernetes-engine/docs/concepts/preemptible-vm
Interesting. Btw this can be achieved if the same MachineClass is updated with new values. The values will be in effect only when the new machine is created or old...
Overall sounds like a good idea to me. The only part, we might want to consider is, if there are constant failures, such machines could stack up, and lead to...
>And I've witnessed that all nodes were get replaces when the load balancer of shoot apiserver was unhealthy and lost all local data. I think we have not faced it...
@rfranzke commented on Apr 29 ``` What happened: MCM does not update the .status.failedMachine of the MachineDeployment after the .status.lastOperation of the Machine changes (e.g., from Failed -> Processing (e.g.,...
Sure, sounds good. The major part of it is for internal usage, and only an aspect is for end-users where we want to offer better observability for the worker-machines.
Dupe of https://github.com/gardener/machine-controller-manager/issues/476 . Closing in favor of the other.