From fa42054588eea18256cfd521d3e973c69f7f9999 Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Tue, 12 Mar 2024 12:28:10 -0400 Subject: [PATCH 1/2] Add restrictions to agent upgrade docs --- .../fleet/upgrade-elastic-agent.asciidoc | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc index c00c80cbe..ad0706123 100644 --- a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc +++ b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc @@ -35,6 +35,22 @@ Docker images. For a detailed view of the {agent} upgrade process and the interactions between {fleet}, {agent}, and {es}, refer to the link:https://github.com/elastic/elastic-agent/blob/main/docs/upgrades.md[Communications amongst components] diagram in the `elastic-agent` GitHub repository. +[discrete] +[[upgrade-agent-restrictions]] +== Restrictions + +Note the following restrictions with upgrading an {agent}: + +* {agent} cannot be upgraded to a version higher than the highest currently installed version of {fleet-server}. +* To be upgradeable, {agent} must not be running inside a container. +* To be upgradeable in a Linux environment, {agent} must be running as a service. The Linux Tar install instructions for {agent} provided in {fleet} include the commands to run it as a service. {agent} RPM and DEB system packages cannot be upgraded through {fleet}. + +These restrictions apply whether you are upgrading {agents} individually or in bulk. In the event that an upgrade isn't elligible, {fleet} generates a warning message when you attempt the upgrade. + +[discrete] +[[upgrade-agent]] +== Upgrading {agent} + To upgrade your {agent}s, go to *Management > {fleet} > Agents* in {kib}. You can perform the following upgrade-related actions: @@ -62,7 +78,6 @@ can perform the following upgrade-related actions: |=== - [discrete] [[upgrade-an-agent]] == Upgrade a single {agent} From fff169fb8005de0e3f395df80ee91447fdafdf6f Mon Sep 17 00:00:00 2001 From: David Kilfoyle Date: Wed, 13 Mar 2024 06:08:18 -0400 Subject: [PATCH 2/2] Fix spelling of 'eligible' --- docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc index ad0706123..53295829c 100644 --- a/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc +++ b/docs/en/ingest-management/fleet/upgrade-elastic-agent.asciidoc @@ -45,7 +45,7 @@ Note the following restrictions with upgrading an {agent}: * To be upgradeable, {agent} must not be running inside a container. * To be upgradeable in a Linux environment, {agent} must be running as a service. The Linux Tar install instructions for {agent} provided in {fleet} include the commands to run it as a service. {agent} RPM and DEB system packages cannot be upgraded through {fleet}. -These restrictions apply whether you are upgrading {agents} individually or in bulk. In the event that an upgrade isn't elligible, {fleet} generates a warning message when you attempt the upgrade. +These restrictions apply whether you are upgrading {agents} individually or in bulk. In the event that an upgrade isn't eligible, {fleet} generates a warning message when you attempt the upgrade. [discrete] [[upgrade-agent]]