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

New Annotation reboot-required #702

Closed
timo-42 opened this issue Nov 15, 2022 · 2 comments · Fixed by #749
Closed

New Annotation reboot-required #702

timo-42 opened this issue Nov 15, 2022 · 2 comments · Fixed by #749

Comments

@timo-42
Copy link

timo-42 commented Nov 15, 2022

Hi

We have some workload in the cluster, which can not be moved at will and requires maintenance windows. It would be much easier for our tools to move stuff around if Kured would set an annotation like weave.works/kured-reboot-required=true and we must not fall back to access an Prometheus.

weave.works/kured-most-recent-reboot-needed does not work for us, since it is only set when the reboot process is already started. We need an indicator beforehand, so we don't schedule long running stuff on it and move single instances in their respective maintenance window from the node.

Is this something the community would be interested in?

@github-actions
Copy link

This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days).

@jackfrancis
Copy link
Collaborator

not stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants