-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider cluster.x-k8s.io/remediate-machine annotated when selecting the machine to be remediate #11385
Comments
This issue is currently awaiting triage. If CAPI contributors determine this is a relevant issue, they will accept it by applying the The 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. |
/triage accepted Also not sure about changes in the MHC controller, but we'll figure it out |
Hi, Is this being worked on as part of any other PR or Can I contribute? Thanks |
Feel free to go ahead, thx! |
Is there any reference available to ease my understanding. |
Not sure, @fabriziopandini ? |
Relevant code:
|
/help |
@fabriziopandini: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
Thanks for the reference, I will check. |
Made an attempt address this issue via PR #11495 with changes only for KCP, Added relevant UT as well. Please take a look and help in clarifying on my understanding and approach. Based on the early feedback will proceed with missing parts. Thanks |
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
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.
The text was updated successfully, but these errors were encountered: