-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Fix maintenance options for rolling upgrades #133369
[Fleet] Fix maintenance options for rolling upgrades #133369
Conversation
Pinging @elastic/fleet (Team:Fleet) |
dbd9511
to
c130aac
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the tests!
💛 Build succeeded, but was flakyFailed CI StepsTest Failures
Metrics [docs]Async chunks
To update your PR or re-run it, just comment with: cc @nchaulet |
(cherry picked from commit eaca3c7)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit eaca3c7) Co-authored-by: Nicolas Chaulet <[email protected]>
Summary
Resolve #133113
Fix available maintenance options for rolling upgrade:
Immediatly
should be available even for more than 10 agentsImmediatly
should be the default for <= 10 agents1 hour
should be the default for > 10 agentsI added some unit test to validate the default value depending on the agent count.