feat: allow staggered reboot of K3s cluster nodes #661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Without specifying any new options, the reboot workflow runs like before; master nodes just got another check for being online.
As an option, you can now specify if you want to have a staggered reboot, i.e. not so many machines rebooting concurrently. It is then also possible to add a wait after rebooting a single machine/a few machines. The instructions on how to set these two options should become clear when reading the documentation.
Checklist
site.ymlplaybookreset.ymlplaybook