Fleet and Elastic Agent 8.17.1

edit

Review important information about the Fleet and Elastic Agent 8.17.1 release.

Breaking changes

edit

Breaking changes can prevent your application from optimal operation and performance. Before you upgrade, review the breaking changes, then mitigate the impact to your application.

Elastic Agent
  • Elastic Agent Docker images for Elastic Cloud have been reverted from having been based off of Ubuntu 24.04 to being based off of Ubuntu 20.04. This is to ensure compatibility with Elastic Cloud Enterprise, support for new Wolfi-based images, and for GNU C Library (glibc) compatibility. #6393

New features

edit

The 8.17.1 release Added the following new and notable features.

Enhancements

edit
Elastic Agent
  • Respond with an error message in case the user running the enroll command and the user who is the owner of the Elastic Agent program files don’t match. #6144 #4889
  • Implement the MarshalJSON method on the component.Component struct, so that when the component model is logged, the output does not contain any secrets that might be part of the component model. #6329 #5675

Bug fixes

edit
Fleet Server
  • Do not set the unenrolled_at attribute when the audit/unenroll API is called. #4221 #6213
  • Remove PGP endpoint auth requirement so that air-gapped Elastic Agents can retreive a PGP key from Fleet Server. #4256 #4255
Elastic Agent
  • During uninstall, call the audit or unenroll API before components are stopped, if Elastic Agent is running a Fleet Server instance. #6085 #5752
  • Update OTel components to v0.1156.0. #6391
  • Restore the cloud-defend binary which was accidentally removed in version 8.17.0. #6470 #6469