Madhav Bhargava
Madhav Bhargava
To add a bit of context. We are constructing a flow which has several steps (some are parallel and some are sequential). What is common is all of these have...
It was suggested that we create another issue for taking care of refactoring. [#5741](https://github.com/gardener/gardener/pull/5741/) is time sensitive and needs to go in first. There is an ongoing effort to even...
I completely agree with you that we should not create new technical debt when the new changes are not yet merged to master which is why i left a review...
@timuthy Agreed. >If the refactoring was a prerequisite for https://github.com/gardener/gardener/pull/5471, then we should have done it first or along the way to a certain extent like Boy Scout Rule suggests....
> Seems like @timuthy was right after all Well i waited for response for https://github.com/gardener/gardener/issues/5977#issuecomment-1129795851 and then finally gave up. I see a lot of code with extremely long functions...
It all started with an original question: `A simple fix that is proposed to tackle the issue of orphan collecting machines during migration of control plane still has a gap...
/remove-lifecycle rotten
>Is it possible to set/mutate those hints ourself, so that we get what we need, because the logic to not set the hints is indeed flawed in our case AFAIK...
> The HighAvailability structure could also be part of SeedSettings. IIRC, you rather wanted it to place in the spec directly w/o remembering the reason. We discussed this some time...