diff --git a/changelog/8.19.17.asciidoc b/changelog/8.19.17.asciidoc new file mode 100644 index 00000000000..d6faef5f60c --- /dev/null +++ b/changelog/8.19.17.asciidoc @@ -0,0 +1,59 @@ +// begin 8.19.17 relnotes + +[[release-notes-8.19.17]] +== 8.19.17 + +Review important information about the 8.19.17 release. + + + + + + + + + +[discrete] +[[new-features-8.19.17]] +=== New features + +The 8.19.17 release adds the following new and notable features. + + + + +* Add Azure Monitor receiver to EDOT Collector. https://github.com/elastic/elastic-agent/pull/14443[#14443] +* Change `bulk_response_filter_path` in elasticsearch exporter configurations to match beats. https://github.com/elastic/elastic-agent/pull/14452[#14452] https://github.com/elastic/elastic-agent/issues/12688[#12688] +* Add Azure auth extension to EDOT Collector. https://github.com/elastic/elastic-agent/pull/14665[#14665] + + +[discrete] +[[enhancements-8.19.17]] +=== Enhancements + + + + +* Disable TLS certificate hot-reload by default. https://github.com/elastic/elastic-agent/pull/14599[#14599] +* Update OTel Collector components to v0.153.0. https://github.com/elastic/elastic-agent/pull/14902[#14902] + + + + +[discrete] +[[bug-fixes-8.19.17]] +=== Bug fixes + + + + +* Preserve live install during upgrade cleanup and report aborted upgrades to Fleet. https://github.com/elastic/elastic-agent/pull/14714[#14714] +* Apply policy log level changes after an agent restart. https://github.com/elastic/elastic-agent/pull/14430[#14430] https://github.com/elastic/elastic-agent/issues/13196[#13196] +* Notify endpoint-security just before symlink swap, not before upgrade attempt. https://github.com/elastic/elastic-agent/pull/14481[#14481] +* Honour `--path.logs` when running `elastic-agent run`. https://github.com/elastic/elastic-agent/pull/14476[#14476] https://github.com/elastic/elastic-agent/issues/13320[#13320] +* Notify Fleet of agent uninstall before marking the installation directory for removal. https://github.com/elastic/elastic-agent/pull/14581[#14581] https://github.com/elastic/elastic-agent/issues/14142[#14142] +* Read TLS config from environment variables in container mode. https://github.com/elastic/elastic-agent/pull/14758[#14758] +* Fix container config override inconsistencies. https://github.com/elastic/elastic-agent/pull/14758[#14758] +* Fix a bug where an empty request body could be sent after failing over to an alternate Fleet host. https://github.com/elastic/elastic-agent/pull/14844[#14844] https://github.com/elastic/elastic-agent/issues/14773[#14773] + +// end 8.19.17 relnotes diff --git a/changelog/8.19.17.yaml b/changelog/8.19.17.yaml new file mode 100644 index 00000000000..7a483e91f0e --- /dev/null +++ b/changelog/8.19.17.yaml @@ -0,0 +1,207 @@ +version: 8.19.17 +entries: + - kind: feature + summary: Add Azure Monitor receiver to EDOT Collector. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14443 + issue: [] + impact: "" + action: "" + timestamp: 1771884267 + file: + name: 1771884267-add-azure-monitor-receiver-to-edot-collector.yaml + checksum: 094233164734be7485b683e033a6ea25b3b92bda + - kind: bug-fix + summary: Preserve live install during upgrade cleanup and report aborted upgrades to Fleet + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14714 + issue: [] + impact: "" + action: "" + timestamp: 1777551882 + file: + name: 1777551882-drosiek-marker-stale.yaml + checksum: 7007cf607ed0cddef1891599315f7e55847fb6a8 + - kind: bug-fix + summary: Policy log level changes are applied after an agent restart + description: | + After an agent had been restarted, changing the log level in the Fleet + policy had no effect, the agent kept reporting and using the previous log + level. Policy log level changes now take effect on agents that have already + been restarted. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14430 + issue: + - https://github.com/elastic/elastic-agent/issues/13196 + impact: "" + action: "" + timestamp: 1778149614 + file: + name: 1778149614-fix-policy-log-level-after-restart.yaml + checksum: c68013c1d45bdba2c12706d0b90d36a7b6e897da + - kind: bug-fix + summary: Notify endpoint-security just before symlink swap, not before upgrade attempt + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14481 + issue: [] + impact: "" + action: "" + timestamp: 1779219800 + file: + name: 1779219800-fix-notify-endpoint-security-just-before-symlink-swap,-not-before-upgrade-attempt.yaml + checksum: f50d6e73b1e272a00be49db675c34143ec304108 + - kind: bug-fix + summary: Honour --path.logs when running elastic-agent run + description: | + When --path.logs is explicitly set on the CLI, the agent now writes logs to the specified path even if the configuration file has agent.logging.to_stderr: true (the shipped default). + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14476 + issue: + - https://github.com/elastic/elastic-agent/issues/13320 + impact: "" + action: "" + timestamp: 1779269825 + file: + name: 1779269825-fix-run-path-logs.yaml + checksum: 01027703efba99afcb91879f7f5d6a40202dddab + - kind: feature + summary: Change bulk_response_filter_path in elasticsearch exporter configurations to match beats. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14452 + issue: + - https://github.com/elastic/elastic-agent/issues/12688 + impact: "" + action: "" + timestamp: 1779393592 + file: + name: 1779393592-change-bulk_response_filter_path-in-elasticsearch-exporter-configurations.yaml + checksum: 2a9fc6198aa397564fdfbe7866a195215c954215 + - kind: other + summary: upgrade NPM to 11.14.1 on wolfi images + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14473 + issue: [] + impact: "" + action: "" + timestamp: 1779396962 + file: + name: 1779396962-heartbeat-bump-npm-11.14.1.yaml + checksum: 521b42499f203d4abf531b8b404d2779fabfa4d2 + - kind: feature + summary: Add Azure auth extension to EDOT Collector + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14665 + issue: [] + impact: "" + action: "" + timestamp: 1779748227 + file: + name: 1779748227-Add-Azure-auth-extension-to-EDOT-Collector.yaml + checksum: 315fbe489a68dd799808b438889dc2b8eadf0959 + - kind: enhancement + summary: Disable TLS certificate hot-reload by default + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14599 + issue: [] + impact: "" + action: "" + timestamp: 1779933797 + file: + name: 1779933797-disable-tls-certificate-hot-reload-by-default.yaml + checksum: 67d7d7daf6bc9068b004f7bf1da08281b9fae3a2 + - kind: bug-fix + summary: Move fleet uninstall notification before installation directory removal as likely fix for runtime panic during uninstall on Windows. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14581 + issue: + - https://github.com/elastic/elastic-agent/issues/14142 + impact: "" + action: "" + timestamp: 1779979535 + file: + name: 1779979535-move-fleet-uninstall-notification-before-installation-directory-removal.yaml + checksum: 37511da15155992574844203e56a71d6cf5656e2 + - kind: bug-fix + summary: Read TLS config from environment variables in container mode + description: TLS certificate paths will now always be read from ELASTIC_AGENT_CERT and ELASTIC_AGENT_CERT_KEY in container mode rather than reading from potentially stale fleet.enc values. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14758 + issue: [] + impact: "" + action: "" + timestamp: 1779995943 + file: + name: 1779995943-read-container-tls-from-env.yaml + checksum: 811169545b21d2614cf29e08920e2180f4063567 + - kind: bug-fix + summary: Fix container config override inconsistencies + description: Fixes a bug where container-mode overrides were correctly applied to the running agent but were overwritten by fleet.enc before being passed to the coordinator. This could result in incorrect config diagnostics and unnecessary restarts on policy updates. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14758 + issue: [] + impact: "" + action: "" + timestamp: 1779996772 + file: + name: 1779996772-fix-container-override-inconsistencies.yaml + checksum: f67af5ec0a67ea14b617b18cb7f6872bc56f6a75 + - kind: bug-fix + summary: Fix bug where an empty request body could be sent after failing over to an alternate fleet host. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14844 + issue: + - https://github.com/elastic/elastic-agent/issues/14773 + impact: "" + action: "" + timestamp: 1780926122 + file: + name: 1780926122-fix-bug-where-an-empty-request-body-could-be-sent-after-failing-over-to-an-alternate-fleet-host..yaml + checksum: 617d9eb2d47fa7ff90c7df3e82031c02a97b3746 + - kind: enhancement + summary: Update OTel Collector components to v0.153.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14902 + issue: [] + impact: "" + action: "" + timestamp: 1781512468 + file: + name: 1781512468-update-otel-components-to-v0.153.0.yaml + checksum: f9f924c97b15b6f86e968672802e7632ed53261e + - kind: other + summary: Bump NPM to 11.17.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/14963 + issue: [] + impact: "" + action: "" + timestamp: 1781639318 + file: + name: 1781639318-heartbeat-bump-npm-11.17.0.yaml + checksum: 5721066e381b7a8a848ba90ed049716c14032860 diff --git a/changelog/fragments/1771884267-add-azure-monitor-receiver-to-edot-collector.yaml b/changelog/fragments/1771884267-add-azure-monitor-receiver-to-edot-collector.yaml deleted file mode 100644 index 2a5799f88b4..00000000000 --- a/changelog/fragments/1771884267-add-azure-monitor-receiver-to-edot-collector.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: feature - -summary: Add Azure Monitor receiver to EDOT Collector. - -component: elastic-agent diff --git a/changelog/fragments/1777551882-drosiek-marker-stale.yaml b/changelog/fragments/1777551882-drosiek-marker-stale.yaml deleted file mode 100644 index 53c04109feb..00000000000 --- a/changelog/fragments/1777551882-drosiek-marker-stale.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Preserve live install during upgrade cleanup and report aborted upgrades to Fleet - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1778149614-fix-policy-log-level-after-restart.yaml b/changelog/fragments/1778149614-fix-policy-log-level-after-restart.yaml deleted file mode 100644 index 5000b3ce3a3..00000000000 --- a/changelog/fragments/1778149614-fix-policy-log-level-after-restart.yaml +++ /dev/null @@ -1,49 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user's deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Policy log level changes are applied after an agent restart - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: | - After an agent had been restarted, changing the log level in the Fleet - policy had no effect, the agent kept reporting and using the previous log - level. Policy log level changes now take effect on agents that have already - been restarted. - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/13196 diff --git a/changelog/fragments/1779219800-fix-notify-endpoint-security-just-before-symlink-swap,-not-before-upgrade-attempt.yaml b/changelog/fragments/1779219800-fix-notify-endpoint-security-just-before-symlink-swap,-not-before-upgrade-attempt.yaml deleted file mode 100644 index ded99879115..00000000000 --- a/changelog/fragments/1779219800-fix-notify-endpoint-security-just-before-symlink-swap,-not-before-upgrade-attempt.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Notify endpoint-security just before symlink swap, not before upgrade attempt - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1779269825-fix-run-path-logs.yaml b/changelog/fragments/1779269825-fix-run-path-logs.yaml deleted file mode 100644 index 9829e5f880d..00000000000 --- a/changelog/fragments/1779269825-fix-run-path-logs.yaml +++ /dev/null @@ -1,12 +0,0 @@ -kind: bug-fix - -summary: Honour --path.logs when running elastic-agent run - -description: > - When --path.logs is explicitly set on the CLI, the agent now writes logs to - the specified path even if the configuration file has - agent.logging.to_stderr: true (the shipped default). - -component: elastic-agent - -issue: https://github.com/elastic/elastic-agent/issues/13320 diff --git a/changelog/fragments/1779393592-change-bulk_response_filter_path-in-elasticsearch-exporter-configurations.yaml b/changelog/fragments/1779393592-change-bulk_response_filter_path-in-elasticsearch-exporter-configurations.yaml deleted file mode 100644 index d0c6c00bf0a..00000000000 --- a/changelog/fragments/1779393592-change-bulk_response_filter_path-in-elasticsearch-exporter-configurations.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Change bulk_response_filter_path in elasticsearch exporter configurations to match beats. - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/14452 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/12688 diff --git a/changelog/fragments/1779396962-heartbeat-bump-npm-11.14.1.yaml b/changelog/fragments/1779396962-heartbeat-bump-npm-11.14.1.yaml deleted file mode 100644 index 4a2fbf7053b..00000000000 --- a/changelog/fragments/1779396962-heartbeat-bump-npm-11.14.1.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: other - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: upgrade NPM to 11.14.1 on wolfi images - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1779748227-Add-Azure-auth-extension-to-EDOT-Collector.yaml b/changelog/fragments/1779748227-Add-Azure-auth-extension-to-EDOT-Collector.yaml deleted file mode 100644 index 06ff95f146a..00000000000 --- a/changelog/fragments/1779748227-Add-Azure-auth-extension-to-EDOT-Collector.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Add Azure auth extension to EDOT Collector - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1779933797-disable-tls-certificate-hot-reload-by-default.yaml b/changelog/fragments/1779933797-disable-tls-certificate-hot-reload-by-default.yaml deleted file mode 100644 index aac6b01fbd8..00000000000 --- a/changelog/fragments/1779933797-disable-tls-certificate-hot-reload-by-default.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Disable TLS certificate hot-reload by default - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1779979535-move-fleet-uninstall-notification-before-installation-directory-removal.yaml b/changelog/fragments/1779979535-move-fleet-uninstall-notification-before-installation-directory-removal.yaml deleted file mode 100644 index 05631e775c3..00000000000 --- a/changelog/fragments/1779979535-move-fleet-uninstall-notification-before-installation-directory-removal.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Move fleet uninstall notification before installation directory removal as likely fix for runtime panic during uninstall on Windows. - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: "elastic-agent" - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/14581 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/14142 diff --git a/changelog/fragments/1779995943-read-container-tls-from-env.yaml b/changelog/fragments/1779995943-read-container-tls-from-env.yaml deleted file mode 100644 index 4b528c7c4ac..00000000000 --- a/changelog/fragments/1779995943-read-container-tls-from-env.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Read TLS config from environment variables in container mode - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: TLS certificate paths will now always be read from ELASTIC_AGENT_CERT and ELASTIC_AGENT_CERT_KEY in container mode rather than reading from potentially stale fleet.enc values. - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1779996772-fix-container-override-inconsistencies.yaml b/changelog/fragments/1779996772-fix-container-override-inconsistencies.yaml deleted file mode 100644 index 0af932975fd..00000000000 --- a/changelog/fragments/1779996772-fix-container-override-inconsistencies.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Fix container config override inconsistencies - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: Fixes a bug where container-mode overrides were correctly applied to the running agent but were overwritten by fleet.enc before being passed to the coordinator. This could result in incorrect config diagnostics and unnecessary restarts on policy updates. - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1780926122-fix-bug-where-an-empty-request-body-could-be-sent-after-failing-over-to-an-alternate-fleet-host..yaml b/changelog/fragments/1780926122-fix-bug-where-an-empty-request-body-could-be-sent-after-failing-over-to-an-alternate-fleet-host..yaml deleted file mode 100644 index 915e7725fa5..00000000000 --- a/changelog/fragments/1780926122-fix-bug-where-an-empty-request-body-could-be-sent-after-failing-over-to-an-alternate-fleet-host..yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Fix bug where an empty request body could be sent after failing over to an alternate fleet host. - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: "elastic-agent" - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/14773 diff --git a/changelog/fragments/1781512468-update-otel-components-to-v0.153.0.yaml b/changelog/fragments/1781512468-update-otel-components-to-v0.153.0.yaml deleted file mode 100644 index 7a6a49f2582..00000000000 --- a/changelog/fragments/1781512468-update-otel-components-to-v0.153.0.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Update OTel Collector components to v0.153.0 - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1781639318-heartbeat-bump-npm-11.17.0.yaml b/changelog/fragments/1781639318-heartbeat-bump-npm-11.17.0.yaml deleted file mode 100644 index 8aa8d5bed6d..00000000000 --- a/changelog/fragments/1781639318-heartbeat-bump-npm-11.17.0.yaml +++ /dev/null @@ -1,45 +0,0 @@ -# REQUIRED -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: other - -# REQUIRED for all kinds -# Change summary; a 80ish characters long description of the change. -summary: Bump NPM to 11.17.0 - -# REQUIRED for breaking-change, deprecation, known-issue -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# REQUIRED for breaking-change, deprecation, known-issue -# impact: - -# REQUIRED for breaking-change, deprecation, known-issue -# action: - -# REQUIRED for all kinds -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# AUTOMATED -# OPTIONAL to manually add other PR URLs -# PR URL: A link the PR that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -# pr: https://github.com/owner/repo/1234 - -# AUTOMATED -# OPTIONAL to manually add other issue URLs -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -# issue: https://github.com/owner/repo/1234