-
Notifications
You must be signed in to change notification settings - Fork 260
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
plugin for drain decisions #620
Labels
stalebot-ignore
To NOT let the stalebot update or close the Issue / PR
Type: Enhancement
New feature or request
Projects
Comments
Hello, thanks for the suggestion. It is an interesting idea and I will add it to the list for further consideration for v2 (currently in development). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue to never become stale, please ask a maintainer to apply the "stalebot-ignore" label. |
snay2
added
stalebot-ignore
To NOT let the stalebot update or close the Issue / PR
and removed
stale
Issues / PRs with no activity
labels
May 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
stalebot-ignore
To NOT let the stalebot update or close the Issue / PR
Type: Enhancement
New feature or request
Describe the feature
when deciding if a node should be terminates (for example for scheduled maintainance) we want to say "don't do it now if the cluster is in trouble" by for example looking at the current node health (tainted / notread / custom node statuses) across the cluster.
Is the feature request related to a problem?
No
Describe alternatives you've considered
Built-in logic would not work since these decisions could be very custom.
The text was updated successfully, but these errors were encountered: