-
Notifications
You must be signed in to change notification settings - Fork 204
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
Cron schedule for node reboots #891
Comments
Hi @robinbobst, One important question which came to my mind: Now (with the reboot-days and -time) there's a timeframe where kured is allowed to reboot nodes. A cron works differently and specifies a recurring timestamp, not a timeframe. As the cluster normally has multiple nodes and the full-reboot can take several hours, a single timestamp, described as a cron would not be enough... |
Hi @ckotzbauer Thanks for your fast response. Yes you are right regarding the timestamp. Just like with the option I would look at the cron feature as an extension of the The config would look something like this:
|
Okay, thanks for the explanations. I'm now sure that the cron-pattern is the wrong way to achieve this. When it should be used together with the existing flags, its not very transparent to the user what would happen and which of the (partially overlapping) behaviours takes place. You can't use the |
Hi @ckotzbauer You are right, I was so focused on my usecase that I didn't even pay attention to the other fields of the cron. Yes a new flag with |
We have same usecase, but with slightly different requirements. That way it's easy to configure "reboot every Mondays, from 2am to 7am at most every two weeks" or "every 3 months" Doesn't colide with day-of-month, both could work together nicely. For our usecase I am more interested to limit the frequency. |
@robinbobst @ant31 I like the approach of @leonnicolas and I think it might cover your needs as well, what do you think? |
@ckotzbauer, yes it matches 100% the feature request, thank you for the quick review ! Not sure it matches @robinbobst. |
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). |
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). |
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). |
Hi there
I would like to use Kured because it sounds like a useful tool which would be very beneficial in our environment
But we have the problem that in our environment node restarts are only allowed on certain maintenance windows which happen every month at the same time.
Is it planned to extend Kured with a cron schedule in the future.
So that these reboots can be scheduled using cron schedules.
example:
5 4 2 * *
At the moment you can only configure on which days kured is allowed to reboot the nodes.
Thank you for your feedback and efforts
The text was updated successfully, but these errors were encountered: