Consider cluster.x-k8s.io/remediate-machine annotated when selecting the machine to be remediate

[fabriziopandini]

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

As an operator, I want CAPI to try to remediate machines annotated with cluster.x-k8s.io/remediate-machine before other machines (also to be remediated, but not hand picked by the operator)

Detailed Description

CAPI should give priority to machine annotated with cluster.x-k8s.io/remediate-machine when selecting the machine to be remediated (thus giving priority to machine picked by the user for remediation)

Anything else you would like to add?

Note, this should be implemented in few places

• MHC (Not 100% sure, but worth to check)
• KCP (Machines with the annotation should be picked first for remediation)
• MS (Machines with the annotation should be sorted as first for remediation)

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]

/triage accepted

Also not sure about changes in the MHC controller, but we'll figure it out

[Karthik-K-N]

Hi, Is this being worked on as part of any other PR or Can I contribute? Thanks

[sbueringer]

Feel free to go ahead, thx!

[Karthik-K-N]

Is there any reference available to ease my understanding.

[sbueringer]

Not sure, @fabriziopandini ?