IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Fleet and Elastic Agent 8.11.3 Fleet and Elastic Agent 8.11.1 »
Elastic Docs ›Fleet and Elastic Agent Guide [8.11] ›Release notes

Fleet and Elastic Agent 8.11.2

edit

Fleet and Elastic Agent 8.11.2

edit

Review important information about Fleet Server and Elastic Agent for the 8.11.2 release.

The memory leak known issue that affects Windows users running Elastic Agent is resolved in this release. If you’re currently on Elastic Agent version 8.11.0 or 8.11.1, we strongly recommend upgrading to 8.11.2 or a later release to avoid the issue. If you’re on an earlier version, avoid upgrading to version 8.11.0 or 8.11.1 and update directly to version 8.11.2 or later.

Known issues

edit
Triggering Elastic Agent upgrades from Kibana Fleet UI in an air-gapped environment will fail

Details

When attempting to upgrade an Elastic Agent, Kibana tries to access https://www.elastic.co/api/product_versions. In an air-gapped environment, this call will be blocked and the upgrade flow will therefore be blocked too.

Upgrade Kibana to version 8.11.3 to solve the issue.

Current stack version is not in the list of Elastic Agent versions in Kibana Fleet UI

Details

On the Fleet UI in Kibana:

  • When adding a new Elastic Agent, the user interface shows a previous version instead of the current version.
  • When you attempt an upgrade, the modal window shows an earlier version as the latest version.

Impact

You can use the following steps as a workaround:

When upgrading Elastic Agent currently on versions 8.10.4 or earlier (simpler)

  1. Open the Fleet UI. Under the Agents tab select Upgrade agent from the actions menu. The version field in the Upgrade agent UI allows you to enter any version.
  2. Enter 8.11.0 or whichever version you want to upgrade the Elastic Agents to. Do not choose a version later than the version of Kibana or Fleet Server that you’re running.

When upgrading Elastic Agent currently on any version (more complex, requires API)

  1. Open Kibana and navigate to Management → Dev Tools.

  2. Choose one of the API requests below and submit it through the console. Each of the requests uses version 8.11.0 as an example, but this can be changed to any available version.

    • To upgrade a single Elastic Agent to any version, run:

      POST kbn:/api/fleet/agents/<Elastic Agent ID>/upgrade
{"version":"8.11.0"}

    • To upgrade a set of Elastic Agents based on a known set of agent IDs, run:

      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "version":"8.11.0",
  "agents":["<Elastic Agent ID>","<Another Elastic Agent ID>"],
  "start_time":"2023-11-10T09:41:39.850Z"
}

    • To upgrade a set of Elastic Agents running a specific policy, and below a specific version (for example, 8.11.0), run:

      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "agents": "fleet-agents.policy_id:<Elastic Fleet Policy ID> and fleet-agents.agent.version<<VERSION>",
  "version": "8.11.0"
}
      POST kbn:/api/fleet/agents/bulk_upgrade
{
  "agents": "fleet-agents.policy_id:uuid1-uuid2-uuid3-uuid4 and fleet-agents.agent.version<8.11.0",
  "version": "8.11.0"
}

To find the ID for any Elastic Agent, open the Agents tab in Fleet and select View agent from the Actions menu. The agent ID and other details are shown.

To learn more about these requests, refer to the Fleet API documentation.

Enhancements

edit
Fleet
  • Improve UX for policy secrets. #171405
Elastic Agent
  • Add configuration parameters for the Kubernetes leader_election provider. #3625
  • Update NodeJS version bundled with Heartbeat to v18.18.2. #3655
  • Update Go version to 1.20.11. #3748

Bug fixes

edit
Fleet
  • Support integration secrets in a local package registry with variables secret: true and required: false. #172078
  • Fix agent metrics retrieval on the agent list page, previously displaying N/A for metrics for users with more than 10 agents. #172016
  • Only add time_series_metric if TSDB is enabled. #171712
  • Fix inability to upgrade agents from version 8.10.4 to version 8.11. #170974
Elastic Agent
  • Fix logging calls that have missing arguments. #3679
  • Fix Fleet-managed Elastic Agent ignoring the agent.download.proxy_url setting after a policy is updated. #3803 #3560
  • Properly convert component error fields to YAML in agent diagnostics. #3835 #2940
« Fleet and Elastic Agent 8.11.3 Fleet and Elastic Agent 8.11.1 »