From 58b871a059b5d5e869c34899103ec7a41efee478 Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Thu, 14 Aug 2025 15:45:01 +0200 Subject: [PATCH 1/2] Clarify Elastic Agent upgrade rollouts --- reference/fleet/upgrade-elastic-agent.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md index a2a200decf..0160d5c975 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -101,6 +101,7 @@ You can do rolling upgrades to avoid exhausting network resources when updating 5. Upgrade the agents. +Note that agents in a rollout period have the status `Updating` until the upgrade is complete, even if the upgrade has not started yet. ## Schedule an upgrade [schedule-agent-upgrade] @@ -245,7 +246,9 @@ To configure an automatic rollout of a new minor or patch version to a percentag 7. You can then add a different target version, and specify the percentage of agents you want to be upgraded to that version. The total percentage of agents to be upgraded cannot exceed 100%. 8. Click **Save**. -Once the configuration is saved, an asynchronous task runs every 30 minutes, gradually upgrading the agents in the policy to the specified target version. +Once the configuration is saved, an asynchronous task runs every 30 minutes, upgrading the agents in the policy to the specified target version. + +If the number of agents to be upgraded is greater or equal to 10, a rollout period based on this number is automatically applied. In case of any failed upgrades, the upgrades are retried with exponential backoff mechanism until the upgrade is successful, or the maximum number of retries is reached. Note that the maximum number of retries is the number of [configured retry delays](#auto-upgrade-settings). From b2381e825834a4526532292afd956b4ce0f0eb73 Mon Sep 17 00:00:00 2001 From: Jill Guyonnet Date: Mon, 18 Aug 2025 09:55:54 +0200 Subject: [PATCH 2/2] Update reference/fleet/upgrade-elastic-agent.md Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> --- reference/fleet/upgrade-elastic-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md index 0160d5c975..b078426734 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -248,7 +248,7 @@ To configure an automatic rollout of a new minor or patch version to a percentag Once the configuration is saved, an asynchronous task runs every 30 minutes, upgrading the agents in the policy to the specified target version. -If the number of agents to be upgraded is greater or equal to 10, a rollout period based on this number is automatically applied. +If the number of agents to be upgraded is greater than or equal to 10, a rollout period is automatically applied. The rollout duration is either 10 minutes or `nAgents * 0.03` seconds, whichever is greater. In case of any failed upgrades, the upgrades are retried with exponential backoff mechanism until the upgrade is successful, or the maximum number of retries is reached. Note that the maximum number of retries is the number of [configured retry delays](#auto-upgrade-settings).