From c04b2139e01c30ecedc6879b855e4fdc87aa2f97 Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Fri, 5 Sep 2025 10:36:14 +0200 Subject: [PATCH 1/5] Add Independent Agent Release doc --- reference/fleet/fleet-agent-release.md | 18 ++++++++++++++++++ reference/fleet/toc.yml | 1 + reference/fleet/upgrade-elastic-agent.md | 4 +++- 3 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 reference/fleet/fleet-agent-release.md diff --git a/reference/fleet/fleet-agent-release.md b/reference/fleet/fleet-agent-release.md new file mode 100644 index 0000000000..7617e06a05 --- /dev/null +++ b/reference/fleet/fleet-agent-release.md @@ -0,0 +1,18 @@ +--- +navigation_title: "{{agent}} release" +mapped_pages: + - https://www.elastic.co/guide/en/fleet/current/fleet-agent-release.html +applies_to: + stack: ga +products: + - id: fleet + - id: elastic-agent +--- + +# {{agent}} release process [fleet-agent-release] + +{{agent}} follows a release process aligned with the broader Elastic Stack release schedule. Changes and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md). + +## Independent Agent Release + +Independent Agent Release (IAR) is a fast-track release process for {{agent}} and Endpoint, designed to deliver critical fixes and updates independently of the full stack release. The IAR version format appends a build identifier `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. diff --git a/reference/fleet/toc.yml b/reference/fleet/toc.yml index 35bf978861..a18c168983 100644 --- a/reference/fleet/toc.yml +++ b/reference/fleet/toc.yml @@ -19,6 +19,7 @@ toc: - file: fleet-server-monitoring.md - file: install-elastic-agents.md children: + - file: fleet-agent-release.md - file: install-fleet-managed-elastic-agent.md - file: install-standalone-elastic-agent.md children: diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md index b078426734..9e4b723ae9 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -80,7 +80,9 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c 3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**. - In certain cases the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field. + {{kib}} provides a list of available {{agent}} versions for upgrade. A version number ending with a build identifier `+build{yyyymmddhhmm}` indicates an [Independent Agent Release version](./fleet-agent-release.md#independent-agent-release). + + In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field. :::{image} images/upgrade-agent-custom.png :alt: Menu for upgrading a single {{agent}} From 5e4911fb504b3d606c2a5fb408a76c4e2d49f492 Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Fri, 5 Sep 2025 16:13:47 +0200 Subject: [PATCH 2/5] Feedback --- reference/fleet/fleet-agent-release-process.md | 18 ++++++++++++++++++ reference/fleet/fleet-agent-release.md | 18 ------------------ reference/fleet/toc.yml | 2 +- reference/fleet/upgrade-elastic-agent.md | 2 +- 4 files changed, 20 insertions(+), 20 deletions(-) create mode 100644 reference/fleet/fleet-agent-release-process.md delete mode 100644 reference/fleet/fleet-agent-release.md diff --git a/reference/fleet/fleet-agent-release-process.md b/reference/fleet/fleet-agent-release-process.md new file mode 100644 index 0000000000..40398b1749 --- /dev/null +++ b/reference/fleet/fleet-agent-release-process.md @@ -0,0 +1,18 @@ +--- +navigation_title: "{{agent}} release process" +applies_to: + stack: ga +products: + - id: fleet + - id: elastic-agent +--- + +# {{agent}} release process [fleet-agent-release-process] + +{{agent}} follows a release process aligned with the broader {{stack}} release schedule. The latest features, enhancements, and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md). + +## Independent agent release + +The independent agent release (IAR) is a hotfix release process for {{agent}} and {{elastic-defend}}, designed to deliver critical fixes and updates independently of the full stack release. The IAR process is more conservative than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an IAR hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch. + +The IAR version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. diff --git a/reference/fleet/fleet-agent-release.md b/reference/fleet/fleet-agent-release.md deleted file mode 100644 index 7617e06a05..0000000000 --- a/reference/fleet/fleet-agent-release.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -navigation_title: "{{agent}} release" -mapped_pages: - - https://www.elastic.co/guide/en/fleet/current/fleet-agent-release.html -applies_to: - stack: ga -products: - - id: fleet - - id: elastic-agent ---- - -# {{agent}} release process [fleet-agent-release] - -{{agent}} follows a release process aligned with the broader Elastic Stack release schedule. Changes and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md). - -## Independent Agent Release - -Independent Agent Release (IAR) is a fast-track release process for {{agent}} and Endpoint, designed to deliver critical fixes and updates independently of the full stack release. The IAR version format appends a build identifier `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. diff --git a/reference/fleet/toc.yml b/reference/fleet/toc.yml index a18c168983..a08b40b87f 100644 --- a/reference/fleet/toc.yml +++ b/reference/fleet/toc.yml @@ -19,7 +19,7 @@ toc: - file: fleet-server-monitoring.md - file: install-elastic-agents.md children: - - file: fleet-agent-release.md + - file: fleet-agent-release-process.md - file: install-fleet-managed-elastic-agent.md - file: install-standalone-elastic-agent.md children: diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md index 9e4b723ae9..6c5e9624fc 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -80,7 +80,7 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c 3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**. - {{kib}} provides a list of available {{agent}} versions for upgrade. A version number ending with a build identifier `+build{yyyymmddhhmm}` indicates an [Independent Agent Release version](./fleet-agent-release.md#independent-agent-release). + {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-release). In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field. From 7e17047dac7c3532444cea6b38074e362f2ec511 Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Mon, 8 Sep 2025 10:17:23 +0200 Subject: [PATCH 3/5] Remove use of acronym --- reference/fleet/fleet-agent-release-process.md | 8 +++++--- reference/fleet/upgrade-elastic-agent.md | 2 +- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/reference/fleet/fleet-agent-release-process.md b/reference/fleet/fleet-agent-release-process.md index 40398b1749..d6b1469ebc 100644 --- a/reference/fleet/fleet-agent-release-process.md +++ b/reference/fleet/fleet-agent-release-process.md @@ -9,10 +9,12 @@ products: # {{agent}} release process [fleet-agent-release-process] +## Scheduled releases + {{agent}} follows a release process aligned with the broader {{stack}} release schedule. The latest features, enhancements, and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md). -## Independent agent release +## Independent {{agent}} releases -The independent agent release (IAR) is a hotfix release process for {{agent}} and {{elastic-defend}}, designed to deliver critical fixes and updates independently of the full stack release. The IAR process is more conservative than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an IAR hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch. +Independent {{agent}} releases deliver critical fixes and updates for {{agent}} and {{elastic-defend}}, independently of the full stack release. This is a more conservative process than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an independent {{agent}} hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch. -The IAR version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. +In independent {{agent}} releases, the version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. diff --git a/reference/fleet/upgrade-elastic-agent.md b/reference/fleet/upgrade-elastic-agent.md index 6c5e9624fc..85cb2d7051 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -80,7 +80,7 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c 3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**. - {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-release). + {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-releases). In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field. From 52e65189af7813e9b659ea059cdb8639b2975d62 Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Mon, 8 Sep 2025 11:00:36 +0200 Subject: [PATCH 4/5] Feedback --- reference/fleet/fleet-agent-release-process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/fleet/fleet-agent-release-process.md b/reference/fleet/fleet-agent-release-process.md index d6b1469ebc..52b2c69dee 100644 --- a/reference/fleet/fleet-agent-release-process.md +++ b/reference/fleet/fleet-agent-release-process.md @@ -13,8 +13,8 @@ products: {{agent}} follows a release process aligned with the broader {{stack}} release schedule. The latest features, enhancements, and fixes are documented in the [release notes](../../release-notes/fleet-elastic-agent/index.md). -## Independent {{agent}} releases +## Independent {{agent}} releases [independent-agent-releases] Independent {{agent}} releases deliver critical fixes and updates for {{agent}} and {{elastic-defend}}, independently of the full stack release. This is a more conservative process than a typical patch release, and only modifies the specific {{agent}} components needed for a targeted fix. For example, an independent {{agent}} hotfix release for {{elastic-defend}} would only change the endpoint-security executable, with the remaining executables being exactly those released in the previous patch. -In independent {{agent}} releases, the version format appends a build identifier in the format `+build{yyyymmddhhmm}` to the semantic version it is based on, where `{yyyymmddhhmm}` is the release timestamp of the build. +In independent {{agent}} releases, a build identifier is appended to the semantic version of the base release in the format `+build{yyyymmddhhmm}`, where `{yyyymmddhhmm}` is the release timestamp of the build. From 801de1e0ba2031280cce07d634773f08db0e6e6e Mon Sep 17 00:00:00 2001 From: jillguyonnet Date: Mon, 8 Sep 2025 11:10:42 +0200 Subject: [PATCH 5/5] Fix missing substitution --- 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 85cb2d7051..85b1243555 100644 --- a/reference/fleet/upgrade-elastic-agent.md +++ b/reference/fleet/upgrade-elastic-agent.md @@ -80,7 +80,7 @@ With the right [subscription level](https://www.elastic.co/subscriptions), you c 3. In the Upgrade agent window, select or specify an upgrade version and click **Upgrade agent**. - {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent agent release version](./fleet-agent-release-process.md#independent-agent-releases). + {{kib}} provides a list of the {{agent}} versions available for upgrade. A version number ending with a build identifier in the format `+build{yyyymmddhhmm}` indicates an [independent {{agent}} release version](./fleet-agent-release-process.md#independent-agent-releases). In certain cases, the latest available {{agent}} version may not be recognized by {{kib}}. For instance, this occurs when the {{kib}} version is lower than the {{agent}} version. You can specify a custom version for {{agent}} to upgrade to by entering the version into the **Upgrade version** text field.