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

Add agent upgrade retry doc #2230

Merged
merged 3 commits into from
Oct 24, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,11 @@ maintenance window during which the upgrades will occur. If your {stack}
subscription level supports it, you can schedule upgrades to occur at a specific
date and time.

In most failure cases the {agent} may retry an upgrade after a short wait. The
wait durations between retries are: 1m, 5m, 10m, 15m, 30m, and 1h. During this
time, the {agent} may show up as "retrying" in the {fleet} UI. Note that you
can abort an upgrade that is being retried. See <<abort-agent-upgrade>>.

This approach simplifies the process of keeping your agents up to date. It also
saves you time because you don’t need third-party tools or processes to
manage upgrades.
Expand Down Expand Up @@ -87,7 +92,7 @@ image::images/rolling-agent-upgrade.png[Menu for bulk upgrading {agent}s]

. Select the amount of time available for the maintenance window. The upgrades
are spread out uniformly across this maintenance window to avoid exhausting
network resources.
network resources.
+
To force selected agents to upgrade immediately when the upgrade is
triggered, select **Immediately**. Avoid using this setting for batches of more
Expand Down