Skip to content

Commit

Permalink
Add Fleet and Elastic Agent 8.2.0 relnotes (elastic#1810)
Browse files Browse the repository at this point in the history
* Add Fleet and Elastic Agent 8.2.0 relnotes

* Apply suggestions from code review

* Remove agent-upgrade-fails-with-failed-binary-verification from troubleshooting topic
  • Loading branch information
dedemorton authored Apr 26, 2022
1 parent 59b54f9 commit 75ed28e
Show file tree
Hide file tree
Showing 3 changed files with 228 additions and 17 deletions.
2 changes: 1 addition & 1 deletion index.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,6 @@ include::troubleshooting/troubleshooting.asciidoc[leveloffset=+2]

include::troubleshooting/faq.asciidoc[leveloffset=+2]

include::release-notes/release-notes-8.1.asciidoc[leveloffset=+1]
include::release-notes/release-notes-8.2.asciidoc[leveloffset=+1]

include::elastic-agent/install-fleet-managed-agent.asciidoc[leveloffset=+2]
227 changes: 227 additions & 0 deletions release-notes/release-notes-8.2.asciidoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,227 @@
// Use these for links to issue and pulls.
:kib-issue: https://github.com/elastic/kibana/issues/
:kib-pull: https://github.com/elastic/kibana/pull/
:agent-issue: https://github.com/elastic/elastic-agent/issues/
:agent-pull: https://github.com/elastic/elastic-agent/pull/
:fleet-server-issue: https://github.com/elastic/beats/issues/fleet-server/
:fleet-server-pull: https://github.com/elastic/beats/pull/fleet-server/


[[release-notes]]
= Release notes

This section summarizes the changes in each release.

* <<release-notes-8.2.0>>


Also see:

* {kibana-ref}/release-notes.html[{kib} release notes]
* {beats-ref}/release-notes.html[{beats} release notes]

// begin 8.2.0 relnotes

[[release-notes-8.2.0]]
== {fleet} and {agent} 8.2.0

Review important information about the {fleet} and {agent} 8.2.0 release.

[discrete]
[[breaking-changes-8.2.0]]
=== Breaking changes

There are no breaking changes for {fleet} or {agent} in this release.

[discrete]
[[known-issues-8.2.0]]
=== Known issues

[[known-issue-issue-kibana-130758]]
.During package upgrade, legacy component templates are not removed
[%collapsible]
====
*Details*
In 8.2.0, when you upgrade an existing package, legacy `@settings` and
`@mappings` component templates are not removed. These templates are deprecated
in favor of the new `@package` component template.
*Impact* +
The legacy templates do not cause issues, but you might want to deleted them
because they are no longer used.
To find and delete legacy component templates:
. In {kib}, go to *Stack Management > Index Management* and click
*Component Templates*.
. Click `Not in use` to filter out component templates that are still in use.
. If the list contains component templates that end in `@mappings` or
`@settings`, use the Actions menu to delete them.
====

[discrete]
[[enhancements-8.2.0]]
=== Enhancements

{fleet}::
* beta[] Add a {ls} output type to {fleet} settings. {kib-issue}104987[#104987]
* Merge the settings and mappings component templates into `@package`.
{kib-pull}128498[#128498]
* Redesign the agent flyout. {kib-pull}128381[#128381]
* Add a link from agent details page to agent dashboard. {kib-pull}127882[#127882]
* Update add agent instructions in {fleet}-managed mode for Kubernetes. {kib-pull}127703[#127703]
* Add `time_series_metric` mapping for `metric_type` package field. {kib-pull}126322[#126322]
* Add support for dimension field. {kib-pull}[#126257]
* Move mappings from index template to component template. {kib-pull}124013[#124013]

{agent}::
* Update ack response schema and processing; add retrier for acks. {agent-pull}200[#200]
* Enhance error messages and logs for process start. {agent-pull}225[#225]
* Change the default policy selection logic. When the agent has no policy ID or
name defined, it will fall back to defaults (defined by
`$FLEET_SERVER_POLICY_ID` and `$FLEET_DEFAULT_TOKEN_POLICY_NAME` environment
variables respectively). {agent-pull}226[#226]
* Add Elastic APM instrumentation. {agent-pull}180[#180]
* Agent can be built for `darwin/arm64`. When it's built for both
`darwin/arm64` and `darwin/adm64` a universal binary is also built and packaged. {agent-pull}203[#203]
* Add support for Cloudbeat. {agent-pull}179[#179]
* Fix download verification in snapshot builds. {agent-issue}252[#252]
* Add support for kubernetes cronjobs. {agent-pull}279[#279]

[discrete]
[[bug-fixes-8.2.0]]
=== Bug fixes

{fleet}::
* There are no bug fixes for {fleet} in this release.

{agent}::
* Move `context cancelled` error from {fleet} gateway into debug level.
{agent-pull}187[#187]
* Update library containerd to 1.5.10. {agent-pull}186[#186]
* Add fleet-server to output of elastic-agent inspect output command (and
diagnostic bundle). {agent-pull}243[#243]
* Update API calls that the agent makes to {kib} when running the container
command. {agent-pull}253[#253]
* Fix diagnostics collect log names on Windows machines. The command now ignores
failures. AgentID is included in diagnostics (and diagnostics collect) output.
{agent-issue}81[#81] {agent-issue}92[#92] {agent-issue}190[#190]
{agent-pull}262[#262]

// end 8.2.0 relnotes

// ---------------------
//TEMPLATE
//Use the following text as a template. Remember to replace the version info.

// begin 8.2.x relnotes

//[[release-notes-8.2.x]]
//== {fleet} and {agent} 8.2.x

//Review important information about the {fleet} and {agent} 8.2.x release.

//[discrete]
//[[security-updates-8.2.x]]
//=== Security updates

//{fleet}::
//* add info

//{agent}::
//* add info

//[discrete]
//[[breaking-changes-8.2.x]]
//=== Breaking changes

//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.

//[discrete]
//[[breaking-PR#]]
//.Short description
//[%collapsible]
//====
//*Details* +
//<Describe new behavior.> For more information, refer to {kibana-pull}PR[#PR].
//*Impact* +
//<Describe how users should mitigate the change.> For more information, refer to {fleet-guide}/fleet-server.html[Fleet Server].
//====
//[discrete]
//[[known-issues-8.2.x]]
//=== Known issues
//[[known-issue-issue#]]
//.Short description
//[%collapsible]
//====
//*Details*
//<Describe known issue.>
//*Impact* +
//<Describe impact or workaround.>
//====
//[discrete]
//[[deprecations-8.2.x]]
//=== Deprecations
//The following functionality is deprecated in 8.2.x, and will be removed in
//8.2.x. Deprecated functionality does not have an immediate impact on your
//application, but we strongly recommend you make the necessary updates after you
//upgrade to 8.2.x.
//{fleet}::
//* add info
//{agent}::
//* add info
//[discrete]
//[[new-features-8.2.x]]
//=== New features
//The 8.2.x release adds the following new and notable features.
//{fleet}::
//* add info
//{agent}::
//* add info
//[discrete]
//[[enhancements-8.2.x]]
//=== Enhancements
//{fleet}::
//* add info
//{agent}::
//* add info
//[discrete]
//[[bug-fixes-8.2.x]]
//=== Bug fixes
//{fleet}::
//* add info
//{agent}::
//* add info
// end 8.2.x relnotes
16 changes: 0 additions & 16 deletions troubleshooting/troubleshooting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,22 +25,6 @@ Running {agent} standalone? Also refer to <<debug-standalone-agents>>.
//TODO: Improve how content is organized in this section, perhaps by breaking
//it down into sections like Agent, Fleet Server, etc.

[discrete]
[[agent-upgrade-fails-with-failed-binary-verification]]
== {agent} upgrade fails with `failed verification of agent binary` error

There is a known issue in {agent} version 8.1.1 and 8.1.2 that causes agent
binary verification to fail with the following message:

[source,text]
----
[elastic_agent][error] failed to dispatch actions, error: failed verification of agent binary: 2 errors occurred:
fetching asc file from '/opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.asc': open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.asc: no such file or directory
open /opt/Elastic/Agent/data/elastic-agent-7f30bb/downloads/elastic-agent-<version>-linux-x86_64.tar.gz.sha512: no such file or directory
----

For more information about resolving this problem, see <<known-issues-8.1.1>>.

[discrete]
[[agents-in-cloud-stuck-at-updating]]
== {agent}s hosted on {ecloud} are stuck in `Updating` or `Offline`
Expand Down

0 comments on commit 75ed28e

Please sign in to comment.