You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
I'm assuming update operator is rebooting one node at a time. I would propose to allow configuring the time delay between node reboots. Locksmithd has a hardcoded rebootDelay of 5 mins but I would prefer much slower rollout of updates and want it to be configurable.
The text was updated successfully, but these errors were encountered:
It would be nice to have an option for the delay. However, the update-operator is a state machine which performs a number of coordinated actions, we can't simply sleep or it'll introduce issues down the road.
Technically, you could have a pre-reboot pod that waits for your desired period right now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm assuming update operator is rebooting one node at a time. I would propose to allow configuring the time delay between node reboots. Locksmithd has a hardcoded rebootDelay of 5 mins but I would prefer much slower rollout of updates and want it to be configurable.
The text was updated successfully, but these errors were encountered: