Skip to content
Merged
Show file tree
Hide file tree
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
20 changes: 20 additions & 0 deletions reference/fleet/fleet-agent-release-process.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
navigation_title: "{{agent}} release process"
applies_to:
stack: ga
products:
- id: fleet
- id: elastic-agent
---

# {{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}} 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, 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.
1 change: 1 addition & 0 deletions reference/fleet/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ toc:
- file: fleet-server-monitoring.md
- file: install-elastic-agents.md
children:
- file: fleet-agent-release-process.md
- file: install-fleet-managed-elastic-agent.md
- file: install-standalone-elastic-agent.md
children:
Expand Down
4 changes: 3 additions & 1 deletion reference/fleet/upgrade-elastic-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.

:::{image} images/upgrade-agent-custom.png
:alt: Menu for upgrading a single {{agent}}
Expand Down