Skip to content
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

Do not start patch or upgrade if cluster is not healthy and any node is cordoned #163

Open
Martin-Weiss opened this issue Nov 3, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@Martin-Weiss
Copy link

Is your feature request related to a problem? Please describe.
I want to patch and update the nodes automatically (not just rke2 or k3s but also the operating system) but the upgrade should only start if the health of the cluster is fine and i.e. there are no prometheus alerts or only "some" and in case there is no node cordoned before starting..

Describe the solution you'd like
Allow specification of blocking alerts / whitelist of alerts.
Check cluster health / node status before starting.

This should be a configuration option in the plan..

Describe alternatives you've considered
We have been using kured in the past which can check for actual alerts and also has some sort of reboot control..
https://github.com/weaveworks/kured
Maybe we can integrate some of that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants