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 7.14.1 Fleet APIs »
Elastic Docs ›Fleet and Elastic Agent Guide [7.14] ›Release notes

Fleet and Elastic Agent 7.14.0

edit

Fleet and Elastic Agent 7.14.0

edit

Review important information about the Fleet and Elastic Agent 7.14.0 releases.

Known issues

edit
Credentials potentially exposed in .fleet-* and .kibana* indices

Details

Credentials that you provide for an agent or integration policy are stored in Elasticsearch. They can be read by any user who has read permissions to the .fleet-* and .kibana* indices in Elasticsearch. By default these are the superuser, fleet-server service account tokens, and the kibana_system user. These secrets are also included in agent policies and shared with agents via Fleet through TLS. When you use the Elastic Agent installer and enroll agents in Fleet, the policies are stored on the host file system and, by default, can only be read by root.

Impact

To avoid exposing secrets, restrict access to the .fleet-* and .kibana* indices to trusted users. Do not change file ownership or permissions on policy files stored on the host file system unless you can secure the files from malicious users.

Elastic Agent fails to start correctly when enrolled in Fleet through a proxy

Details

When you attempt to enroll an Elastic Agent in Fleet and specify the proxy-url flag, the status of the agent hangs at Updating in Fleet, and the Elastic Agent fails to start correctly.

Impact

Do not enroll Elastic Agents through a proxy until this issue is fixed. #27114 #27187

Fleet Server policy setup failure may result in Fleet not starting

Details

During setup of the default Fleet Server policy, an error may occur, such as a network error or connectivity issue, that results in a default policy with no input. Fleet will be unable to start.

Impact

To fix this problem:

  1. Delete the default Fleet Server policy saved object:

    1. In Kibana, open the main menu, then go to Management > Dev Tools > Console.

    2. In the Console, send the following request:

      POST .kibana/_delete_by_query?q=ingest-agent-policies.is_default_fleet_server:true
  2. Go to Management > Fleet to force reloading of the object.

New features

edit

The 7.14.0 release adds the following new and notable features.

Fleet
  • Moves integrations to a separate app #99848
« Fleet and Elastic Agent 7.14.1 Fleet APIs »