Add a Time-Configurable Parameter for Delay Between Machine Rollouts

[avaneesh634]

What would you like to be added (User Story)?

As a user I would like to have a time configurable parameter for delay between machine rollouts. This delay between machine rollout will help in data sync while using local volumes.

Detailed Description

I would like to introduce a time-configurable parameter to control the delay between machine rollouts. This would help ensure proper data synchronization between replicas using local volumes on the node.

For example, in a Redis quorum setup with a three-node cluster, at least two pods must be running to maintain quorum. If Machine 1 undergoes a rollout, the kubelet on that node restarts. However, before the data sync from other replicas completes, the remaining machines might also roll out, causing their kubelets to go down. As a result, only one pod remains running, failing the quorum requirement and making Redis unavailable.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[sbueringer]

Have you considered using PodDisruptionBudgets?

[fabriziopandini]

I also would like to understand better, because K8s primitives seem a better solution instead of relying on arbitrary timeouts that proved to be racy in many other occasion