-
Notifications
You must be signed in to change notification settings - Fork 117
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
MCM to mark terminating nodes #488
Comments
Sounds like a good idea to me to have an indication on node-object, whenever it's being terminated, likely due to health-conditions. |
I got the information that you are working on a fix for this. Hence assigning you to the issue. /assign @guydaichs |
Hi @prashanth26. Yes, I'm working on this. I noticed that there's already a mechanism for syncing the machine config with a node annotation. However, in my case, I want the annotation to capture a certain transition, and not the current state. So, I was thinking to annotate the node in the WDYT? |
/status in-progress |
/reopen to port this changes on OOT. |
/unassign @guydaichs |
What would you like to be added:
When MCM replaces nodes (unhealthy node termination, node rolling updates, ...), nodes that are being terminated should be marked in some way (e.g. annotation) to reflect the reason of their termination.
Why is this needed:
End-users can setup monitoring for the progress of node rolling updates. If PDBs are used, end-users can automate removal of PDBs from pods that are running on nodes which are being terminated due to health issues.
The text was updated successfully, but these errors were encountered: