Add a configuration flag for Machine Deletion Timeouts

[chatla-telekom]

User Story

As a user I would like to have the possibility for specifying the timeout duration for machine deletion.

Detailed Description

According to the current implementation, the timeout for machine deletion is set to 10 seconds after which the machine is not deleted. This is not feasible in some cases as it leads to orphan machines in the clusters even after they are deleted in the control plane. By having the possibility to configure the machine deletion timeout, CAPI can retry to delete the machine until the timeout set by the user.

If the flag is not set, the timeout would fall back to the default value of 10 seconds.

More about this can be found in this discussion on Slack: https://kubernetes.slack.com/archives/C8TSNPY4T/p1631180381209300

/kind feature

[chatla-telekom]

@MaxRink @schrej

[schrej]

I've already started working on a PR for this, it's just missing tests, which are somewhat tricky to implement.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sbueringer]

/remove-lifecycle stale
PR in progress

[sbueringer]

/lifecycle active
/assign @schrej

[fabriziopandini]

/milestone v1.2