From 44a3924b5ade2b5d0a5ad255b536e79560a75a47 Mon Sep 17 00:00:00 2001 From: Eric Beahan Date: Mon, 28 Jul 2025 13:10:37 -0500 Subject: [PATCH 1/4] clean up fragments --- .../1723829102-Upgrade-to-Go-1.23.0.yaml | 32 -------------- .../1725913991-remove-cloud-defend.yaml | 4 -- ...6144746-container-default-credentials.yaml | 32 -------------- .../1726145045-container-api-key.yaml | 32 -------------- ...6572104-enable-persistence-by-default.yaml | 32 -------------- .../1728332120-Upgrade-to-Go-1.22.8..yaml | 32 -------------- .../1729011748-Add-EDOT-hybrid-mode.yaml | 32 -------------- ...1729630977-Add-filebeat-otel-receiver.yaml | 32 -------------- .../1729750939-crossbuild-debian11.yaml | 4 -- ...-fail-early-fleet-managed-cli-upgrade.yaml | 31 ------------- ...tform-and-os_version-to-host-provider.yaml | 32 -------------- ...-Directory-user-for-unprivileged-mode.yaml | 32 -------------- ...dpoint-security-from-linux-containers.yaml | 30 ------------- ...-re-enable-otel-subcommand-on-Windows.yaml | 32 -------------- ...lastic-defend-cannot-run-in-emulation.yaml | 32 -------------- .../1732187698-update-otel-v0.114.0.yaml | 32 -------------- ...able-error-message-for-enroll-command.yaml | 31 ------------- ...add-GeoIP-processor-to-EDOT-collector.yaml | 32 -------------- ...un-providers-referenced-in-the-policy.yaml | 32 -------------- ...33156311-add-metricbeat-otel-receiver.yaml | 32 -------------- .../1733248787-flag-to-skip-fleet-audit.yaml | 32 -------------- ...d-routing-connector-to-EDOT-collector.yaml | 32 -------------- .../1733390040-update-otel-0.115.0.yaml | 32 -------------- ...dact-common-secrets-in-inspect-output.yaml | 32 -------------- ...-Notify-Fleet-of-uninstall-on-Windows.yaml | 32 -------------- ...etries-for-download-upgrade-verifiers.yaml | 30 ------------- ...dbalancing-exporter-to-EDOT-collector.yaml | 32 -------------- ...-secrets-when-logging-component-model.yaml | 32 -------------- ...hints-inputs-in-agent-container-image.yaml | 32 -------------- .../1734525166-update-otel-v0.116.0.yaml | 32 -------------- ...Logging-to-install,-uninstall,-enroll.yaml | 32 -------------- ...ed-images-with-UBI-minimal-based-ones.yaml | 32 -------------- ...ove-deprecated-list-in-favor-of-items.yaml | 31 ------------- ...llector-in-Helm-kube-stack-deployment.yaml | 32 -------------- ...move-deprecated-path-install-cli-flag.yaml | 30 ------------- ...-log-fleet-enroll-failure-status-code.yaml | 32 -------------- .../1736417404-update-otel-v0.117.0.yaml | 32 -------------- .../1737106864-add_otel_components_cmd.yaml | 32 -------------- ...131552-Changes-to-binary-distribution.yaml | 43 ------------------- .../1737462864-add_k8s_otel_comps.yaml | 32 -------------- ...-force-install-replaces-correct-agent.yaml | 30 ------------- ...ken-change-or-the-agent-is-unenrolled.yaml | 32 -------------- ...b-process-communication-in-containers.yaml | 32 -------------- .../1737666699-Add-filesource-provider.yaml | 34 --------------- ...7648-add-kafkaexporter-otel-collector.yaml | 32 -------------- ...749181-add-jmxreceiver-otel-collector.yaml | 32 -------------- ...750331-add-nopreceiver-otel-collector.yaml | 32 -------------- ...d-context-variable-support-to-outputs.yaml | 34 --------------- ...itions-in-kubernetes_secrets-provider.yaml | 32 -------------- ...1738160406-add_redis_nginx_otel_comps.yaml | 32 -------------- ...ceived-too-many-unathorized-responses.yaml | 30 ------------- .../1738752554-update-otel-v0.119.0.yaml | 32 -------------- ...dd-id-and-replace-token-to-enrollment.yaml | 36 ---------------- ...netes_secrets-provider-secret-logging.yaml | 32 -------------- ...44282-add-MOtel-sample-configurations.yaml | 32 -------------- ...739981369-Fix-deadlock-in-OTelManager.yaml | 34 --------------- ...1-kube-stack-helm-chart-metrics-batch.yaml | 33 -------------- ...pgrade-with-tamper-protected-endpoint.yaml | 30 ------------- ...72-set-replicas-for-gateway-collector.yaml | 32 -------------- ...y-prefix-to-MOTel-host-configurations.yaml | 32 -------------- ...0713597-support-agent-monitoring-ipv6.yaml | 32 -------------- ...-elastic.agent.fips-to-local_metadata.yaml | 34 --------------- ...ate-pbkdf2-settings-when-in-FIPS-mode.yaml | 32 -------------- ...08763-FIPS-Compliant-agent-file-vault.yaml | 35 --------------- ...1741865161-fix-otel-kube-stack-config.yaml | 32 -------------- .../1741897911-fips-to-fips-upgrades.yaml | 30 ------------- ...642-fips-to-fips-upgrade-error-reword.yaml | 29 ------------- .../1743783374-update-otel-v0.121.0.yaml | 32 -------------- ...64-update-otel-components-to-v0.122.0.yaml | 32 -------------- ...059162-send-correct-signal-on-windows.yaml | 32 -------------- .../fragments/1744198660-add-nopexporter.yaml | 32 -------------- ...44839123-fix-MOtel-config-image-value.yaml | 32 -------------- ...44886313-otel_disable_process_scraper.yaml | 38 ---------------- ...163-journalctl-on-all-docker-variants.yaml | 35 --------------- ...77-update-otel-components-to-v0.123.0.yaml | 32 -------------- ...1745923884-deb-rpm-preserve-run-state.yaml | 5 --- ...13477-Retry-enrollment-for-all-errors.yaml | 36 ---------------- .../1746197293-config-rollback-window.yaml | 36 ---------------- ...lment-communication-with-Fleet-Server.yaml | 35 --------------- .../fragments/1746636264-fix-notice.yaml | 35 --------------- .../1746652545-Upgrade-to-Go-1.24.3..yaml | 32 -------------- .../fragments/1746736812-fips-notice.yaml | 32 -------------- .../1747938268-fix-diag-race-condition.yaml | 4 -- ...38-update-otel-components-to-v0.125.0.yaml | 32 -------------- ...176965-add-cumulativetodeltaprocessor.yaml | 32 -------------- ...paths.TempDir-for-diagnostics-actions.yaml | 32 -------------- ...71-add-apmconfig-apikeyauth-extension.yaml | 32 -------------- ...11-for-linux-arm-to-match-linux-amd64.yaml | 32 -------------- ...ile-ownership-check-for-re-enrollment.yaml | 33 -------------- ...01-update-otel-components-to-v0.127.0.yaml | 32 -------------- ...0329445-add-bearertokenauth-extension.yaml | 32 -------------- ...asticsearchexporter-deprecated-config.yaml | 32 -------------- .../1750408426-kube-stack-service-attrs.yaml | 38 ---------------- .../1750412496-bump-apmconfig-extension.yaml | 32 -------------- ...ate-the-elasticinframetrics-processor.yaml | 32 -------------- .../1751029489-synth-upgra-node-v20.yaml | 32 -------------- ...nprivileged-installations-are-in-beta.yaml | 32 -------------- ...ot-collector-include-forwardconnector.yaml | 32 -------------- ...1751444462-add_logs_only_motel_config.yaml | 32 -------------- ...rrect-log-level-for-standalone-agents.yaml | 5 --- ...85-update-otel-components-to-v0.129.0.yaml | 32 -------------- ...568-update-apmconfig-extension-v0.4.0.yaml | 32 -------------- ...date-elastictrace-processor-to-v0.7.0.yaml | 32 -------------- ...update-elasticapm-connector-to-v0.4.0.yaml | 32 -------------- ...update-apikeyauth-extension-to-v0.2.0.yaml | 32 -------------- ...ic-infra-metrics-processor-to-v0.16.0.yaml | 32 -------------- ...ng-issues-inside-runtime-communicator.yaml | 5 --- ...9251-Fixed-SUSE-installation-from-RPM.yaml | 32 -------------- 108 files changed, 3328 deletions(-) delete mode 100644 changelog/fragments/1723829102-Upgrade-to-Go-1.23.0.yaml delete mode 100644 changelog/fragments/1725913991-remove-cloud-defend.yaml delete mode 100644 changelog/fragments/1726144746-container-default-credentials.yaml delete mode 100644 changelog/fragments/1726145045-container-api-key.yaml delete mode 100644 changelog/fragments/1726572104-enable-persistence-by-default.yaml delete mode 100644 changelog/fragments/1728332120-Upgrade-to-Go-1.22.8..yaml delete mode 100644 changelog/fragments/1729011748-Add-EDOT-hybrid-mode.yaml delete mode 100644 changelog/fragments/1729630977-Add-filebeat-otel-receiver.yaml delete mode 100644 changelog/fragments/1729750939-crossbuild-debian11.yaml delete mode 100644 changelog/fragments/1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml delete mode 100644 changelog/fragments/1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.yaml delete mode 100644 changelog/fragments/1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.yaml delete mode 100644 changelog/fragments/1731517501-removed-endpoint-security-from-linux-containers.yaml delete mode 100644 changelog/fragments/1731962301-re-enable-otel-subcommand-on-Windows.yaml delete mode 100644 changelog/fragments/1732110636-elastic-defend-cannot-run-in-emulation.yaml delete mode 100644 changelog/fragments/1732187698-update-otel-v0.114.0.yaml delete mode 100644 changelog/fragments/1732656422-add-actionable-error-message-for-enroll-command.yaml delete mode 100644 changelog/fragments/1732809895-add-GeoIP-processor-to-EDOT-collector.yaml delete mode 100644 changelog/fragments/1732840106-Only-run-providers-referenced-in-the-policy.yaml delete mode 100644 changelog/fragments/1733156311-add-metricbeat-otel-receiver.yaml delete mode 100644 changelog/fragments/1733248787-flag-to-skip-fleet-audit.yaml delete mode 100644 changelog/fragments/1733317274-add-routing-connector-to-EDOT-collector.yaml delete mode 100644 changelog/fragments/1733390040-update-otel-0.115.0.yaml delete mode 100644 changelog/fragments/1733397457-redact-common-secrets-in-inspect-output.yaml delete mode 100644 changelog/fragments/1733768621-Notify-Fleet-of-uninstall-on-Windows.yaml delete mode 100644 changelog/fragments/1733936340-add-retries-for-download-upgrade-verifiers.yaml delete mode 100644 changelog/fragments/1734023789-add-loadbalancing-exporter-to-EDOT-collector.yaml delete mode 100644 changelog/fragments/1734098868-prevent-leaking-secrets-when-logging-component-model.yaml delete mode 100644 changelog/fragments/1734512365-embed-hints-inputs-in-agent-container-image.yaml delete mode 100644 changelog/fragments/1734525166-update-otel-v0.116.0.yaml delete mode 100644 changelog/fragments/1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.yaml delete mode 100644 changelog/fragments/1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.yaml delete mode 100644 changelog/fragments/1735137195-remove-deprecated-list-in-favor-of-items.yaml delete mode 100644 changelog/fragments/1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.yaml delete mode 100644 changelog/fragments/1735664420-remove-deprecated-path-install-cli-flag.yaml delete mode 100644 changelog/fragments/1736002257-log-fleet-enroll-failure-status-code.yaml delete mode 100644 changelog/fragments/1736417404-update-otel-v0.117.0.yaml delete mode 100644 changelog/fragments/1737106864-add_otel_components_cmd.yaml delete mode 100644 changelog/fragments/1737131552-Changes-to-binary-distribution.yaml delete mode 100644 changelog/fragments/1737462864-add_k8s_otel_comps.yaml delete mode 100644 changelog/fragments/1737473147-force-install-replaces-correct-agent.yaml delete mode 100644 changelog/fragments/1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.yaml delete mode 100644 changelog/fragments/1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.yaml delete mode 100644 changelog/fragments/1737666699-Add-filesource-provider.yaml delete mode 100644 changelog/fragments/1737717648-add-kafkaexporter-otel-collector.yaml delete mode 100644 changelog/fragments/1737749181-add-jmxreceiver-otel-collector.yaml delete mode 100644 changelog/fragments/1737750331-add-nopreceiver-otel-collector.yaml delete mode 100644 changelog/fragments/1737816507-Add-context-variable-support-to-outputs.yaml delete mode 100644 changelog/fragments/1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.yaml delete mode 100644 changelog/fragments/1738160406-add_redis_nginx_otel_comps.yaml delete mode 100644 changelog/fragments/1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml delete mode 100644 changelog/fragments/1738752554-update-otel-v0.119.0.yaml delete mode 100644 changelog/fragments/1738784301-Add-id-and-replace-token-to-enrollment.yaml delete mode 100644 changelog/fragments/1739437836-Improve-kubernetes_secrets-provider-secret-logging.yaml delete mode 100644 changelog/fragments/1739544282-add-MOtel-sample-configurations.yaml delete mode 100644 changelog/fragments/1739981369-Fix-deadlock-in-OTelManager.yaml delete mode 100644 changelog/fragments/1740054191-kube-stack-helm-chart-metrics-batch.yaml delete mode 100644 changelog/fragments/1740166208-allow-deb-rpm-upgrade-with-tamper-protected-endpoint.yaml delete mode 100644 changelog/fragments/1740492672-set-replicas-for-gateway-collector.yaml delete mode 100644 changelog/fragments/1740674973-add-ApiKey-prefix-to-MOTel-host-configurations.yaml delete mode 100644 changelog/fragments/1740713597-support-agent-monitoring-ipv6.yaml delete mode 100644 changelog/fragments/1740773781-Add-elastic.agent.fips-to-local_metadata.yaml delete mode 100644 changelog/fragments/1741122475-Validate-pbkdf2-settings-when-in-FIPS-mode.yaml delete mode 100644 changelog/fragments/1741808763-FIPS-Compliant-agent-file-vault.yaml delete mode 100644 changelog/fragments/1741865161-fix-otel-kube-stack-config.yaml delete mode 100644 changelog/fragments/1741897911-fips-to-fips-upgrades.yaml delete mode 100644 changelog/fragments/1742318642-fips-to-fips-upgrade-error-reword.yaml delete mode 100644 changelog/fragments/1743783374-update-otel-v0.121.0.yaml delete mode 100644 changelog/fragments/1744022264-update-otel-components-to-v0.122.0.yaml delete mode 100644 changelog/fragments/1744059162-send-correct-signal-on-windows.yaml delete mode 100644 changelog/fragments/1744198660-add-nopexporter.yaml delete mode 100644 changelog/fragments/1744839123-fix-MOtel-config-image-value.yaml delete mode 100644 changelog/fragments/1744886313-otel_disable_process_scraper.yaml delete mode 100644 changelog/fragments/1745609163-journalctl-on-all-docker-variants.yaml delete mode 100644 changelog/fragments/1745610677-update-otel-components-to-v0.123.0.yaml delete mode 100644 changelog/fragments/1745923884-deb-rpm-preserve-run-state.yaml delete mode 100644 changelog/fragments/1746113477-Retry-enrollment-for-all-errors.yaml delete mode 100644 changelog/fragments/1746197293-config-rollback-window.yaml delete mode 100644 changelog/fragments/1746213492-Add-header-to-enrollment-communication-with-Fleet-Server.yaml delete mode 100644 changelog/fragments/1746636264-fix-notice.yaml delete mode 100644 changelog/fragments/1746652545-Upgrade-to-Go-1.24.3..yaml delete mode 100644 changelog/fragments/1746736812-fips-notice.yaml delete mode 100644 changelog/fragments/1747938268-fix-diag-race-condition.yaml delete mode 100644 changelog/fragments/1749110938-update-otel-components-to-v0.125.0.yaml delete mode 100644 changelog/fragments/1749176965-add-cumulativetodeltaprocessor.yaml delete mode 100644 changelog/fragments/1749742685-Use-paths.TempDir-for-diagnostics-actions.yaml delete mode 100644 changelog/fragments/1749824071-add-apmconfig-apikeyauth-extension.yaml delete mode 100644 changelog/fragments/1749844873-Use-Debian-11-for-linux-arm-to-match-linux-amd64.yaml delete mode 100644 changelog/fragments/1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml delete mode 100644 changelog/fragments/1750008201-update-otel-components-to-v0.127.0.yaml delete mode 100644 changelog/fragments/1750329445-add-bearertokenauth-extension.yaml delete mode 100644 changelog/fragments/1750349806-elasticsearchexporter-deprecated-config.yaml delete mode 100644 changelog/fragments/1750408426-kube-stack-service-attrs.yaml delete mode 100644 changelog/fragments/1750412496-bump-apmconfig-extension.yaml delete mode 100644 changelog/fragments/1750781638-Deprecate-the-elasticinframetrics-processor.yaml delete mode 100644 changelog/fragments/1751029489-synth-upgra-node-v20.yaml delete mode 100644 changelog/fragments/1751037802-Stop-logging-that-unprivileged-installations-are-in-beta.yaml delete mode 100644 changelog/fragments/1751317599-edot-collector-include-forwardconnector.yaml delete mode 100644 changelog/fragments/1751444462-add_logs_only_motel_config.yaml delete mode 100644 changelog/fragments/1751455886-correct-log-level-for-standalone-agents.yaml delete mode 100644 changelog/fragments/1751458785-update-otel-components-to-v0.129.0.yaml delete mode 100644 changelog/fragments/1751536568-update-apmconfig-extension-v0.4.0.yaml delete mode 100644 changelog/fragments/1751638649-update-elastictrace-processor-to-v0.7.0.yaml delete mode 100644 changelog/fragments/1751638799-update-elasticapm-connector-to-v0.4.0.yaml delete mode 100644 changelog/fragments/1751639092-update-apikeyauth-extension-to-v0.2.0.yaml delete mode 100644 changelog/fragments/1751639206-update-elastic-infra-metrics-processor-to-v0.16.0.yaml delete mode 100644 changelog/fragments/1751960319-fix-blocking-issues-inside-runtime-communicator.yaml delete mode 100644 changelog/fragments/1752049251-Fixed-SUSE-installation-from-RPM.yaml diff --git a/changelog/fragments/1723829102-Upgrade-to-Go-1.23.0.yaml b/changelog/fragments/1723829102-Upgrade-to-Go-1.23.0.yaml deleted file mode 100644 index 6bbea61d70d..00000000000 --- a/changelog/fragments/1723829102-Upgrade-to-Go-1.23.0.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: Upgrade-to-Go-1.24.0 - -# 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/elastic/elastic-agent/pull/5309 - -# 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/1725913991-remove-cloud-defend.yaml b/changelog/fragments/1725913991-remove-cloud-defend.yaml deleted file mode 100644 index ddbc4371301..00000000000 --- a/changelog/fragments/1725913991-remove-cloud-defend.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: breaking-change -summary: Remove cloud-defend from agent package -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/5481 diff --git a/changelog/fragments/1726144746-container-default-credentials.yaml b/changelog/fragments/1726144746-container-default-credentials.yaml deleted file mode 100644 index 560262122cf..00000000000 --- a/changelog/fragments/1726144746-container-default-credentials.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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: Remove default credentials when running Elastic Agent in container mode - -# 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: ELASTICSEARCH_USERNAME and ELASTICSEARCH_PASSWORD now need to be explicitly set when running the agent in container mode - -# 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/1726145045-container-api-key.yaml b/changelog/fragments/1726145045-container-api-key.yaml deleted file mode 100644 index 72cf4b5fc1c..00000000000 --- a/changelog/fragments/1726145045-container-api-key.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: Support ELASTICSEARCH_API_KEY environment variable when running in container mode - -# 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/1726572104-enable-persistence-by-default.yaml b/changelog/fragments/1726572104-enable-persistence-by-default.yaml deleted file mode 100644 index e07766a099f..00000000000 --- a/changelog/fragments/1726572104-enable-persistence-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: feature - -# Change summary; a 80ish characters long description of the change. -summary: Enable persistence in the configuration provided with our OTel Collector distribution. - -# 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,otel - -# 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: - -# 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/1728332120-Upgrade-to-Go-1.22.8..yaml b/changelog/fragments/1728332120-Upgrade-to-Go-1.22.8..yaml deleted file mode 100644 index 96b4cf9d7e5..00000000000 --- a/changelog/fragments/1728332120-Upgrade-to-Go-1.22.8..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: security - -# Change summary; a 80ish characters long description of the change. -summary: Upgrade to Go 1.22.8. - -# 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/elastic/elastic-agent/pull/5731 - -# 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/1729011748-Add-EDOT-hybrid-mode.yaml b/changelog/fragments/1729011748-Add-EDOT-hybrid-mode.yaml deleted file mode 100644 index f7ed858e654..00000000000 --- a/changelog/fragments/1729011748-Add-EDOT-hybrid-mode.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 ability to run Elastic Distribution of OTel Collector at the same time as other inputs - -# 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/elastic/elastic-agent/pull/5767 - -# 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/1729630977-Add-filebeat-otel-receiver.yaml b/changelog/fragments/1729630977-Add-filebeat-otel-receiver.yaml deleted file mode 100644 index 2d8a34ddd46..00000000000 --- a/changelog/fragments/1729630977-Add-filebeat-otel-receiver.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: Add filebeat otel receiver - -# 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; a word indicating the component this changeset affects. -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/elastic/elastic-agent/pull/5833 - -# 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/1729750939-crossbuild-debian11.yaml b/changelog/fragments/1729750939-crossbuild-debian11.yaml deleted file mode 100644 index dd3b512f1df..00000000000 --- a/changelog/fragments/1729750939-crossbuild-debian11.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: breaking-change -summary: crossbuild-debian11 -description: We're dropping support for Debian 10, so no need to crossbuild using the outdated image anymore. This also updates the statically linked glibc from 2.19 to 2.31. -component: elastic-agent diff --git a/changelog/fragments/1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml b/changelog/fragments/1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml deleted file mode 100644 index c6c9ecc9097..00000000000 --- a/changelog/fragments/1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml +++ /dev/null @@ -1,31 +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: Detect and fail-early cli upgrades if agent is fleet-managed - -# 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: This change brings restrictions on the upgrade cli command. If an agent is fleet-managed and is running in unprivileged mode, users won't be able to upgrade the agent using the cli. If an agent is fleet-managed and is running privileged, users will only be able to upgrade the agent using the cli if they provide --force flag. - -# 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/elastic/elastic-agent/pull/5864 -# 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/1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.yaml b/changelog/fragments/1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.yaml deleted file mode 100644 index 990a3406908..00000000000 --- a/changelog/fragments/1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.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 os_family, os_platform and os_version to host provider - -# 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/elastic/elastic-agent/pull/5941 - -# 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/integrations/issues/10797 diff --git a/changelog/fragments/1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.yaml b/changelog/fragments/1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.yaml deleted file mode 100644 index fcbf11fd0e7..00000000000 --- a/changelog/fragments/1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.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: Added support for pre-existing Active Directory user for unprivileged mode - -# 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: User can specify custom pre-existing user for running unprivileged mode. This user will be given permissions to log on as a service. - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# 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/elastic/elastic-agent/issues/4585 diff --git a/changelog/fragments/1731517501-removed-endpoint-security-from-linux-containers.yaml b/changelog/fragments/1731517501-removed-endpoint-security-from-linux-containers.yaml deleted file mode 100644 index ee1a49c9c14..00000000000 --- a/changelog/fragments/1731517501-removed-endpoint-security-from-linux-containers.yaml +++ /dev/null @@ -1,30 +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: removed endpoint security from linux containers - -# 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: Removed elastic endpoint security from linux containers as it has a dependency on systemd. - -# 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/elastic/elastic-agent/pull/6016 -# 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/5495 diff --git a/changelog/fragments/1731962301-re-enable-otel-subcommand-on-Windows.yaml b/changelog/fragments/1731962301-re-enable-otel-subcommand-on-Windows.yaml deleted file mode 100644 index 9fc7207dd3e..00000000000 --- a/changelog/fragments/1731962301-re-enable-otel-subcommand-on-Windows.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: re-enable otel subcommand on Windows - -# 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; a word indicating the component this changeset affects. -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/elastic/elastic-agent/pull/6068 - -# 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/4976 diff --git a/changelog/fragments/1732110636-elastic-defend-cannot-run-in-emulation.yaml b/changelog/fragments/1732110636-elastic-defend-cannot-run-in-emulation.yaml deleted file mode 100644 index 9092e92aa97..00000000000 --- a/changelog/fragments/1732110636-elastic-defend-cannot-run-in-emulation.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: Prevent installing Elastic Defend on non native architecture - -# 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/1732187698-update-otel-v0.114.0.yaml b/changelog/fragments/1732187698-update-otel-v0.114.0.yaml deleted file mode 100644 index 157b5697dd3..00000000000 --- a/changelog/fragments/1732187698-update-otel-v0.114.0.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: Update OTel components to v0.114.0 - -# 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/1732656422-add-actionable-error-message-for-enroll-command.yaml b/changelog/fragments/1732656422-add-actionable-error-message-for-enroll-command.yaml deleted file mode 100644 index 5bc0e037318..00000000000 --- a/changelog/fragments/1732656422-add-actionable-error-message-for-enroll-command.yaml +++ /dev/null @@ -1,31 +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: Elastic agent returns an actionable error message when a the use trying to execute the enroll command is not the same as the onwer of the elastic-agent program files - -# 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/elastic/elastic-agent/pull/6144 -# 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/4889 diff --git a/changelog/fragments/1732809895-add-GeoIP-processor-to-EDOT-collector.yaml b/changelog/fragments/1732809895-add-GeoIP-processor-to-EDOT-collector.yaml deleted file mode 100644 index ee1adf50504..00000000000 --- a/changelog/fragments/1732809895-add-GeoIP-processor-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 GeoIP processor 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/1732840106-Only-run-providers-referenced-in-the-policy.yaml b/changelog/fragments/1732840106-Only-run-providers-referenced-in-the-policy.yaml deleted file mode 100644 index a73f073c080..00000000000 --- a/changelog/fragments/1732840106-Only-run-providers-referenced-in-the-policy.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: Only run providers referenced in the policy - -# 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/elastic/elastic-agent/pull/6169 - -# 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/3609 diff --git a/changelog/fragments/1733156311-add-metricbeat-otel-receiver.yaml b/changelog/fragments/1733156311-add-metricbeat-otel-receiver.yaml deleted file mode 100644 index 69938c1288f..00000000000 --- a/changelog/fragments/1733156311-add-metricbeat-otel-receiver.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 metricbeat otel receiver - -# 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; a word indicating the component this changeset affects. -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/elastic/elastic-agent/pull/6182 - -# 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/6138 diff --git a/changelog/fragments/1733248787-flag-to-skip-fleet-audit.yaml b/changelog/fragments/1733248787-flag-to-skip-fleet-audit.yaml deleted file mode 100644 index 023cb7e589f..00000000000 --- a/changelog/fragments/1733248787-flag-to-skip-fleet-audit.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: Add a flag to skip audit/unenroll call to fleet server during uninstall - -# 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: This change adds a flag to skip audit/unenroll call to fleet server. While uninstalling elastic-agent it tries to notify fleet server about the uninstallation. But in somecases users might know that the fleet server is unreachable and this notification logs multiple failures continuously. Adding this flag skips this call. - -# 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/1733317274-add-routing-connector-to-EDOT-collector.yaml b/changelog/fragments/1733317274-add-routing-connector-to-EDOT-collector.yaml deleted file mode 100644 index 8f0632de4a1..00000000000 --- a/changelog/fragments/1733317274-add-routing-connector-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 OpenTelemetry Routing connector 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/1733390040-update-otel-0.115.0.yaml b/changelog/fragments/1733390040-update-otel-0.115.0.yaml deleted file mode 100644 index 97731fd29a7..00000000000 --- a/changelog/fragments/1733390040-update-otel-0.115.0.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: Update OTel components to v0.115.0 - -# 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/1733397457-redact-common-secrets-in-inspect-output.yaml b/changelog/fragments/1733397457-redact-common-secrets-in-inspect-output.yaml deleted file mode 100644 index 52c16241b5b..00000000000 --- a/changelog/fragments/1733397457-redact-common-secrets-in-inspect-output.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: Redact common secrets like API keys and passwords in the output from `inspect` command - -# 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/1733768621-Notify-Fleet-of-uninstall-on-Windows.yaml b/changelog/fragments/1733768621-Notify-Fleet-of-uninstall-on-Windows.yaml deleted file mode 100644 index 6e40d9748e7..00000000000 --- a/changelog/fragments/1733768621-Notify-Fleet-of-uninstall-on-Windows.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 Fleet of uninstall on Windows - -# 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: - -# 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/elastic/elastic-agent/pull/6257 - -# 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/5952 diff --git a/changelog/fragments/1733936340-add-retries-for-download-upgrade-verifiers.yaml b/changelog/fragments/1733936340-add-retries-for-download-upgrade-verifiers.yaml deleted file mode 100644 index 29ece746651..00000000000 --- a/changelog/fragments/1733936340-add-retries-for-download-upgrade-verifiers.yaml +++ /dev/null @@ -1,30 +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: added retries for requesting download verifiers when upgrading the agent - -# 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/elastic/elastic-agent/pull/6276 -# 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/1734023789-add-loadbalancing-exporter-to-EDOT-collector.yaml b/changelog/fragments/1734023789-add-loadbalancing-exporter-to-EDOT-collector.yaml deleted file mode 100644 index 4aa562c412c..00000000000 --- a/changelog/fragments/1734023789-add-loadbalancing-exporter-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 loadbalancing exporter 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/1734098868-prevent-leaking-secrets-when-logging-component-model.yaml b/changelog/fragments/1734098868-prevent-leaking-secrets-when-logging-component-model.yaml deleted file mode 100644 index 1a8c13ff8ba..00000000000 --- a/changelog/fragments/1734098868-prevent-leaking-secrets-when-logging-component-model.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: Prevent leaking secrets when logging the component model - -# 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/1734512365-embed-hints-inputs-in-agent-container-image.yaml b/changelog/fragments/1734512365-embed-hints-inputs-in-agent-container-image.yaml deleted file mode 100644 index c005769ca3a..00000000000 --- a/changelog/fragments/1734512365-embed-hints-inputs-in-agent-container-image.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: Embed hints-based inputs in the Elastic Agent container image. - -# Long description; in case the summary is not enough to describe the change -# this field accommodates a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -description: This change includes the addition of hints-based inputs directly within the Elastic Agent container image, enabling streamlined configurations for input discovery when deployed in containerized environments. - -# 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/elastic/elastic-agent/pull/6381 - -# 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/5661 diff --git a/changelog/fragments/1734525166-update-otel-v0.116.0.yaml b/changelog/fragments/1734525166-update-otel-v0.116.0.yaml deleted file mode 100644 index 85c58010e30..00000000000 --- a/changelog/fragments/1734525166-update-otel-v0.116.0.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: Update OTel components to v0.116.0 - -# 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/1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.yaml b/changelog/fragments/1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.yaml deleted file mode 100644 index b64393d748f..00000000000 --- a/changelog/fragments/1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.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: Windows add Event Logging to install, uninstall, enroll failures - -# 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; a word indicating the component this changeset affects. -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/elastic/elastic-agent/6410 - -# 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/6338 diff --git a/changelog/fragments/1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.yaml b/changelog/fragments/1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.yaml deleted file mode 100644 index 2146ab2cef8..00000000000 --- a/changelog/fragments/1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: Replace default Ubuntu-based images with UBI-minimal-based ones - -# 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/elastic/elastic-agent/pull/6427 - -# 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/1735137195-remove-deprecated-list-in-favor-of-items.yaml b/changelog/fragments/1735137195-remove-deprecated-list-in-favor-of-items.yaml deleted file mode 100644 index 015675d0e8e..00000000000 --- a/changelog/fragments/1735137195-remove-deprecated-list-in-favor-of-items.yaml +++ /dev/null @@ -1,31 +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: removes `list` from kibanaFetchToken in favor of `items` as the former is deprecated and will be removed from the api response - -# 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/elastic/elastic-agent/pull/6437 -# 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/6023 diff --git a/changelog/fragments/1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.yaml b/changelog/fragments/1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.yaml deleted file mode 100644 index eab0eb63e80..00000000000 --- a/changelog/fragments/1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.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 gateway collector in Helm kube-stack deployment - -# 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/1735664420-remove-deprecated-path-install-cli-flag.yaml b/changelog/fragments/1735664420-remove-deprecated-path-install-cli-flag.yaml deleted file mode 100644 index f0a3da1d2db..00000000000 --- a/changelog/fragments/1735664420-remove-deprecated-path-install-cli-flag.yaml +++ /dev/null @@ -1,30 +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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: Removing --path.install option - -# 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/elastic/elastic-agent/pull/6461/files -# 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/2489 diff --git a/changelog/fragments/1736002257-log-fleet-enroll-failure-status-code.yaml b/changelog/fragments/1736002257-log-fleet-enroll-failure-status-code.yaml deleted file mode 100644 index 54e04d76d2f..00000000000 --- a/changelog/fragments/1736002257-log-fleet-enroll-failure-status-code.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: Added logger to print the status and code when enrollment call to fleet failed. - -# 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/elastic/elastic-agent/issues/6287 diff --git a/changelog/fragments/1736417404-update-otel-v0.117.0.yaml b/changelog/fragments/1736417404-update-otel-v0.117.0.yaml deleted file mode 100644 index 9aa0eb36dbf..00000000000 --- a/changelog/fragments/1736417404-update-otel-v0.117.0.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: Update OTel components to v0.117.0 - -# 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/1737106864-add_otel_components_cmd.yaml b/changelog/fragments/1737106864-add_otel_components_cmd.yaml deleted file mode 100644 index a3713df5901..00000000000 --- a/changelog/fragments/1737106864-add_otel_components_cmd.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 `components` command for `otel` mode. - -# 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/1737131552-Changes-to-binary-distribution.yaml b/changelog/fragments/1737131552-Changes-to-binary-distribution.yaml deleted file mode 100644 index ead9992d0de..00000000000 --- a/changelog/fragments/1737131552-Changes-to-binary-distribution.yaml +++ /dev/null @@ -1,43 +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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: Changes to binary distribution - -# 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: | - Default install installs only: - - agentbeat - - endpoint-security - - pf-host-agent - additional flag is added that includes components above and: - - cloudbeat - - apm-server - - fleet-server - - pf-elastic-symbolizer - - pf-elastic-collector - - -# 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/1737462864-add_k8s_otel_comps.yaml b/changelog/fragments/1737462864-add_k8s_otel_comps.yaml deleted file mode 100644 index 660b13e6a40..00000000000 --- a/changelog/fragments/1737462864-add_k8s_otel_comps.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 receivercreator and k8sobserver 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/1737473147-force-install-replaces-correct-agent.yaml b/changelog/fragments/1737473147-force-install-replaces-correct-agent.yaml deleted file mode 100644 index 108e73cda44..00000000000 --- a/changelog/fragments/1737473147-force-install-replaces-correct-agent.yaml +++ /dev/null @@ -1,30 +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: The install command is updated so that if a user installs an agent, while there is already an agent, using the `--force` flag replaces the correct one. - -# 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/elastic/elastic-agent/pull/6559 -# 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/5595 diff --git a/changelog/fragments/1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.yaml b/changelog/fragments/1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.yaml deleted file mode 100644 index c7ad80de6b7..00000000000 --- a/changelog/fragments/1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.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: Fix enrollment for containerised agent when enrollment token changes or the agent is unenrolled - -# 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/elastic/elastic-agent/pull/6568 - -# 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/3586 diff --git a/changelog/fragments/1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.yaml b/changelog/fragments/1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.yaml deleted file mode 100644 index 635a75357d6..00000000000 --- a/changelog/fragments/1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.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: Use a random free port for sub-process communication in containers by default. Avoids port collisions when using host networking in Kubernetes. - -# 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/elastic/elastic-agent/pull/6585 - -# 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/1737666699-Add-filesource-provider.yaml b/changelog/fragments/1737666699-Add-filesource-provider.yaml deleted file mode 100644 index 6ee40c0e8db..00000000000 --- a/changelog/fragments/1737666699-Add-filesource-provider.yaml +++ /dev/null @@ -1,34 +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 filesource provider - -# 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: | - filesource provider watches for changes of the files and updates the values of the variables - when the content of the file changes. - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# 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/elastic/elastic-agent/pull/6587 - -# 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/6362 diff --git a/changelog/fragments/1737717648-add-kafkaexporter-otel-collector.yaml b/changelog/fragments/1737717648-add-kafkaexporter-otel-collector.yaml deleted file mode 100644 index 0212da02750..00000000000 --- a/changelog/fragments/1737717648-add-kafkaexporter-otel-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 kafkaexporter and kafkareceiver 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/elastic/elastic-agent/issues/6562 diff --git a/changelog/fragments/1737749181-add-jmxreceiver-otel-collector.yaml b/changelog/fragments/1737749181-add-jmxreceiver-otel-collector.yaml deleted file mode 100644 index 318230bba20..00000000000 --- a/changelog/fragments/1737749181-add-jmxreceiver-otel-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 jmxreceiver 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/1737750331-add-nopreceiver-otel-collector.yaml b/changelog/fragments/1737750331-add-nopreceiver-otel-collector.yaml deleted file mode 100644 index 9904849ceab..00000000000 --- a/changelog/fragments/1737750331-add-nopreceiver-otel-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 nopreceiver 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/1737816507-Add-context-variable-support-to-outputs.yaml b/changelog/fragments/1737816507-Add-context-variable-support-to-outputs.yaml deleted file mode 100644 index 9d861edf943..00000000000 --- a/changelog/fragments/1737816507-Add-context-variable-support-to-outputs.yaml +++ /dev/null @@ -1,34 +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 context variable support to outputs - -# 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: | - Adds support for using context variable providers in the outputs section of a policy. Includes fallback support - to reference env provider when no provider prefix is provided in the variable. - -# 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/elastic/elastic-agent/pull/6602 - -# 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/6376 diff --git a/changelog/fragments/1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.yaml b/changelog/fragments/1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.yaml deleted file mode 100644 index a73644bf309..00000000000 --- a/changelog/fragments/1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.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: Fix logical race conditions in kubernetes_secrets provider - -# 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/elastic/elastic-agent/pull/6623 - -# 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/6340 diff --git a/changelog/fragments/1738160406-add_redis_nginx_otel_comps.yaml b/changelog/fragments/1738160406-add_redis_nginx_otel_comps.yaml deleted file mode 100644 index 576b9fb0d17..00000000000 --- a/changelog/fragments/1738160406-add_redis_nginx_otel_comps.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 Nginx receiver and Redis receiver OTel components - -# 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/1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml b/changelog/fragments/1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml deleted file mode 100644 index 182e4fa62da..00000000000 --- a/changelog/fragments/1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml +++ /dev/null @@ -1,30 +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: Updated the fleet gateway so that when the number of unauthorized fleet responses exceeds the set limit, instead of unenrolling, the gateway starts checking in less frequently. - -# 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/elastic/elastic-agent/pull/6619 -# 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/5428 diff --git a/changelog/fragments/1738752554-update-otel-v0.119.0.yaml b/changelog/fragments/1738752554-update-otel-v0.119.0.yaml deleted file mode 100644 index c72cf8f99c6..00000000000 --- a/changelog/fragments/1738752554-update-otel-v0.119.0.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: Update OTel components to v0.119.0 - -# 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/1738784301-Add-id-and-replace-token-to-enrollment.yaml b/changelog/fragments/1738784301-Add-id-and-replace-token-to-enrollment.yaml deleted file mode 100644 index 18be580d45a..00000000000 --- a/changelog/fragments/1738784301-Add-id-and-replace-token-to-enrollment.yaml +++ /dev/null @@ -1,36 +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 --id and --replace-token to enrollment - -# 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: | - Add support for --id and --replace-token to the install and enroll command. Add support for ELASTIC_AGENT_ID - and FLEET_REPLACE_TOKEN to the container support the same behavior as the enroll command. Allows the ability to - define a specific ID to use for the Elastic Agent when enrolling into Fleet. The replace-token defines the token - that must be used to re-enroll an Elastic Agent with the same ID as a replacement of the previous Elastic Agent. - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# 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/elastic/elastic-agent/pull/6498 - -# 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/6361 diff --git a/changelog/fragments/1739437836-Improve-kubernetes_secrets-provider-secret-logging.yaml b/changelog/fragments/1739437836-Improve-kubernetes_secrets-provider-secret-logging.yaml deleted file mode 100644 index 5a364cbcac9..00000000000 --- a/changelog/fragments/1739437836-Improve-kubernetes_secrets-provider-secret-logging.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: Improve kubernetes_secrets provider secret logging - -# 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/elastic/elastic-agent/pull/6841 - -# 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/6187 diff --git a/changelog/fragments/1739544282-add-MOtel-sample-configurations.yaml b/changelog/fragments/1739544282-add-MOtel-sample-configurations.yaml deleted file mode 100644 index 94583c945f3..00000000000 --- a/changelog/fragments/1739544282-add-MOtel-sample-configurations.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 MOtel sample configurations - -# 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/elastic/elastic-agent/pull/6630 - -# 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/1739981369-Fix-deadlock-in-OTelManager.yaml b/changelog/fragments/1739981369-Fix-deadlock-in-OTelManager.yaml deleted file mode 100644 index af11a5c5eca..00000000000 --- a/changelog/fragments/1739981369-Fix-deadlock-in-OTelManager.yaml +++ /dev/null @@ -1,34 +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: Fix deadlock in OTelManager - -# 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: | - Fixes a deadlock case in the OTelManager where an Update can occur while an error is also being reported - which causes the communication with the OTelManager to hit a deadlock. - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: - -# 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/elastic/elastic-agent/pull/6927 - -# 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/1740054191-kube-stack-helm-chart-metrics-batch.yaml b/changelog/fragments/1740054191-kube-stack-helm-chart-metrics-batch.yaml deleted file mode 100644 index f94a5ce9866..00000000000 --- a/changelog/fragments/1740054191-kube-stack-helm-chart-metrics-batch.yaml +++ /dev/null @@ -1,33 +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: Fix TSDB version_conflict_engine_exception caused by incorrect kube-stack Helm values - -# 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: Setting non-zero send_batch_max_size for metrics risks TSDB version_conflict_engine_exception as it causes metrics grouping in es exporter to not work properly. - - -# 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/1740166208-allow-deb-rpm-upgrade-with-tamper-protected-endpoint.yaml b/changelog/fragments/1740166208-allow-deb-rpm-upgrade-with-tamper-protected-endpoint.yaml deleted file mode 100644 index bc894982add..00000000000 --- a/changelog/fragments/1740166208-allow-deb-rpm-upgrade-with-tamper-protected-endpoint.yaml +++ /dev/null @@ -1,30 +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: Allow upgrading deb or rpm agents when using Elastic Defend with tamper protection. - -# 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/elastic/elastic-agent/pull/6907 -# 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/6394 diff --git a/changelog/fragments/1740492672-set-replicas-for-gateway-collector.yaml b/changelog/fragments/1740492672-set-replicas-for-gateway-collector.yaml deleted file mode 100644 index b90d805fd4a..00000000000 --- a/changelog/fragments/1740492672-set-replicas-for-gateway-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: set replicas for gateway 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/elastic/elastic-agent/pull/7011 - -# 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/1740674973-add-ApiKey-prefix-to-MOTel-host-configurations.yaml b/changelog/fragments/1740674973-add-ApiKey-prefix-to-MOTel-host-configurations.yaml deleted file mode 100644 index 7a8ef82f9af..00000000000 --- a/changelog/fragments/1740674973-add-ApiKey-prefix-to-MOTel-host-configurations.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: add ApiKey prefix to MOTel host configurations - -# 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/elastic/elastic-agent/pull/7063 - -# 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/1740713597-support-agent-monitoring-ipv6.yaml b/changelog/fragments/1740713597-support-agent-monitoring-ipv6.yaml deleted file mode 100644 index 034b52320ed..00000000000 --- a/changelog/fragments/1740713597-support-agent-monitoring-ipv6.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: support ipv6 host in agent monitoring http config - -# 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/elastic/elastic-agent/pull/7073 - -# 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/1740773781-Add-elastic.agent.fips-to-local_metadata.yaml b/changelog/fragments/1740773781-Add-elastic.agent.fips-to-local_metadata.yaml deleted file mode 100644 index 05793c9ed11..00000000000 --- a/changelog/fragments/1740773781-Add-elastic.agent.fips-to-local_metadata.yaml +++ /dev/null @@ -1,34 +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: Add elastic.agent.fips to local_metadata - -# 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: | - Add elastic.agent.fips (bool) attribute to local_metadata sent with enroll and checkin requests. - The value of this attribute indicates if the agent is a FIPS-capable distribution. - -# 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/elastic/elastic-agent/pull/7112 diff --git a/changelog/fragments/1741122475-Validate-pbkdf2-settings-when-in-FIPS-mode.yaml b/changelog/fragments/1741122475-Validate-pbkdf2-settings-when-in-FIPS-mode.yaml deleted file mode 100644 index f1d70dc1320..00000000000 --- a/changelog/fragments/1741122475-Validate-pbkdf2-settings-when-in-FIPS-mode.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: Validate pbkdf2 settings when in FIPS mode - -# 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/elastic/elastic-agent/pull/7187 - -# 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/1741808763-FIPS-Compliant-agent-file-vault.yaml b/changelog/fragments/1741808763-FIPS-Compliant-agent-file-vault.yaml deleted file mode 100644 index 062dfec148a..00000000000 --- a/changelog/fragments/1741808763-FIPS-Compliant-agent-file-vault.yaml +++ /dev/null @@ -1,35 +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: FIPS-capable agent file vault - -# 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: | - Change elastic file vault implementation to allow variable length salt sizes - only in FIPS enabled agents. Increase default salt size to 16 for FIPS - compliance. Non-FIPS agents are unchanged. - -# 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/elastic/elastic-agent/pull/7360 - -# 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: diff --git a/changelog/fragments/1741865161-fix-otel-kube-stack-config.yaml b/changelog/fragments/1741865161-fix-otel-kube-stack-config.yaml deleted file mode 100644 index cd3db72209e..00000000000 --- a/changelog/fragments/1741865161-fix-otel-kube-stack-config.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: Fix elasticsearch exporter configuration in kube-stack values - -# 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/1741897911-fips-to-fips-upgrades.yaml b/changelog/fragments/1741897911-fips-to-fips-upgrades.yaml deleted file mode 100644 index a1504fe5c14..00000000000 --- a/changelog/fragments/1741897911-fips-to-fips-upgrades.yaml +++ /dev/null @@ -1,30 +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: With this change FIPS-capable agents will only be able to upgrade to other FIPS-capable agents. This change also restricts non-fips to fips upgrades as well. - -# 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/elastic/elastic-agent/pull/7312 -# 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/ingest-dev/issues/4811 diff --git a/changelog/fragments/1742318642-fips-to-fips-upgrade-error-reword.yaml b/changelog/fragments/1742318642-fips-to-fips-upgrade-error-reword.yaml deleted file mode 100644 index a28e1cbd67c..00000000000 --- a/changelog/fragments/1742318642-fips-to-fips-upgrade-error-reword.yaml +++ /dev/null @@ -1,29 +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: Updated the error messages returned for fips upgrades - -# 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/elastic/elastic-agent/pull/7453 -# 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. diff --git a/changelog/fragments/1743783374-update-otel-v0.121.0.yaml b/changelog/fragments/1743783374-update-otel-v0.121.0.yaml deleted file mode 100644 index c4be885ea58..00000000000 --- a/changelog/fragments/1743783374-update-otel-v0.121.0.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: Update OTel components to v0.121.0 - -# 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 \ No newline at end of file diff --git a/changelog/fragments/1744022264-update-otel-components-to-v0.122.0.yaml b/changelog/fragments/1744022264-update-otel-components-to-v0.122.0.yaml deleted file mode 100644 index cb886bffeb1..00000000000 --- a/changelog/fragments/1744022264-update-otel-components-to-v0.122.0.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: Update OTel components to v0.122.0 - -# 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/elastic/elastic-agent/pull/7725 - -# 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/1744059162-send-correct-signal-on-windows.yaml b/changelog/fragments/1744059162-send-correct-signal-on-windows.yaml deleted file mode 100644 index def4cd5b4c6..00000000000 --- a/changelog/fragments/1744059162-send-correct-signal-on-windows.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: Correctly handle sending signal to child process - -# 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/elastic/elastic-agent/pull/7738 - -# 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/6875 diff --git a/changelog/fragments/1744198660-add-nopexporter.yaml b/changelog/fragments/1744198660-add-nopexporter.yaml deleted file mode 100644 index c92cdaa5b5f..00000000000 --- a/changelog/fragments/1744198660-add-nopexporter.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 nopexporter 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/1744839123-fix-MOtel-config-image-value.yaml b/changelog/fragments/1744839123-fix-MOtel-config-image-value.yaml deleted file mode 100644 index 06048a5f3b6..00000000000 --- a/changelog/fragments/1744839123-fix-MOtel-config-image-value.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: Fix Managed OTLP Helm config to use current image repo. - -# 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/1744886313-otel_disable_process_scraper.yaml b/changelog/fragments/1744886313-otel_disable_process_scraper.yaml deleted file mode 100644 index 199992feaa8..00000000000 --- a/changelog/fragments/1744886313-otel_disable_process_scraper.yaml +++ /dev/null @@ -1,38 +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: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: '[otel] Disable process scraper of hostmetrics receiver' - -# 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: | - The process scraper collects metrics for all available processes of a host without an easy way to limit - this to only report top N process for example. This results in quite big amount of timeseries. - Since this is not quite critical for any of the available UIs or dashboards we decide to disable - it temporarily until we find a better solution. Users that specifically need these metrics - can also enable it back manually. - Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/39423. - -# 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/elastic/elastic-agent/pull/7894 - -# 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/1745609163-journalctl-on-all-docker-variants.yaml b/changelog/fragments/1745609163-journalctl-on-all-docker-variants.yaml deleted file mode 100644 index b9b6eeb8ba4..00000000000 --- a/changelog/fragments/1745609163-journalctl-on-all-docker-variants.yaml +++ /dev/null @@ -1,35 +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: | - Ship journalctl in the elastic-agent, elastic-agent-complete, and - elastic-otel-collector Docker images to enable reading journald - logs. Journalctl is not present on *-slim and all Wolfi images. - -# 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/elastic/elastic-agent/pull/7995 - -# 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/beats/issues/44040 diff --git a/changelog/fragments/1745610677-update-otel-components-to-v0.123.0.yaml b/changelog/fragments/1745610677-update-otel-components-to-v0.123.0.yaml deleted file mode 100644 index b8bf671ca8b..00000000000 --- a/changelog/fragments/1745610677-update-otel-components-to-v0.123.0.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: Update OTel components to v0.123.0 - -# 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/elastic/elastic-agent/pull/7996 - -# 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/1745923884-deb-rpm-preserve-run-state.yaml b/changelog/fragments/1745923884-deb-rpm-preserve-run-state.yaml deleted file mode 100644 index 97b15497af8..00000000000 --- a/changelog/fragments/1745923884-deb-rpm-preserve-run-state.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: bug-fix -summary: Preserve agent run state on DEB and RPM upgrades -component: "elastic-agent" -pr: https://github.com/elastic/elastic-agent/pull/7999 -issue: https://github.com/elastic/elastic-agent/issues/3832 diff --git a/changelog/fragments/1746113477-Retry-enrollment-for-all-errors.yaml b/changelog/fragments/1746113477-Retry-enrollment-for-all-errors.yaml deleted file mode 100644 index 18152848b26..00000000000 --- a/changelog/fragments/1746113477-Retry-enrollment-for-all-errors.yaml +++ /dev/null @@ -1,36 +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: Retry enrollment requests on any error - -# 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: | - If any error is encountered during an attempted enrollment, the elastic-agent - will backoff and retry. Add a new --enroll-timeout flag and - FLEET_ENROLL_TIMEOUT env var to set how long it tries for, default 10m. A - negative value disables the timeout. - -# 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/elastic/elastic-agent/pull/8056 - -# 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/1746197293-config-rollback-window.yaml b/changelog/fragments/1746197293-config-rollback-window.yaml deleted file mode 100644 index e379b5bbf5a..00000000000 --- a/changelog/fragments/1746197293-config-rollback-window.yaml +++ /dev/null @@ -1,36 +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: Adds a new configuration setting, `agent.upgrade.rollback.window` - -# 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: | - The value of the `agent.upgrade.rollback.window` setting determines the period after upgrading - Elastic Agent when a rollback to the previous version can be triggered. This is an optional - setting, with a default value of `168h` (7 days). The value can be any string that is parseable - by https://pkg.go.dev/time#ParseDuration. - -# 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/elastic/elastic-agent/pull/8065 - -# 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/6881 diff --git a/changelog/fragments/1746213492-Add-header-to-enrollment-communication-with-Fleet-Server.yaml b/changelog/fragments/1746213492-Add-header-to-enrollment-communication-with-Fleet-Server.yaml deleted file mode 100644 index ccfe06621bf..00000000000 --- a/changelog/fragments/1746213492-Add-header-to-enrollment-communication-with-Fleet-Server.yaml +++ /dev/null @@ -1,35 +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: Use --header from enrollment when communicating with Fleet Server - -# 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: | - The --header option for the enrollment command now adds the headers to the communication with Fleet Server. This - allows a proxy that requires specific headers present for traffic to flow to be placed in front of a Fleet Server - to be used and still allowing the Elastic Agent to enroll. - -# 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/elastic/elastic-agent/pull/8071 - -# 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/6823 diff --git a/changelog/fragments/1746636264-fix-notice.yaml b/changelog/fragments/1746636264-fix-notice.yaml deleted file mode 100644 index 36895c2805c..00000000000 --- a/changelog/fragments/1746636264-fix-notice.yaml +++ /dev/null @@ -1,35 +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: other - -# Change summary; a 80ish characters long description of the change. -summary: NOTICE.txt now contains only those modules that are used by the Elastic Agent binaries. - -# 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: | - Only those modules that the Elastic Agent binaries for various platforms directly - or indirectly depend on are now included in the NOTICE.txt file . Modules used for development - tooling are now excluded from NOTICE.txt. - -# 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/elastic/elastic-agent/pull/8053 - -# 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/1746652545-Upgrade-to-Go-1.24.3..yaml b/changelog/fragments/1746652545-Upgrade-to-Go-1.24.3..yaml deleted file mode 100644 index 2135326ba1c..00000000000 --- a/changelog/fragments/1746652545-Upgrade-to-Go-1.24.3..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: security - -# Change summary; a 80ish characters long description of the change. -summary: Upgrade to Go 1.24.3. - -# 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/elastic/elastic-agent/pull/8109 - -# 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/1746736812-fips-notice.yaml b/changelog/fragments/1746736812-fips-notice.yaml deleted file mode 100644 index 322a8de44d3..00000000000 --- a/changelog/fragments/1746736812-fips-notice.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: other - -# Change summary; a 80ish characters long description of the change. -summary: A new NOTICE file, `NOTICE-fips.txt` is included in FIPS-capable Agent distributions. - -# 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/elastic/elastic-agent/pull/8124 - -# 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/1747938268-fix-diag-race-condition.yaml b/changelog/fragments/1747938268-fix-diag-race-condition.yaml deleted file mode 100644 index ee6a1750147..00000000000 --- a/changelog/fragments/1747938268-fix-diag-race-condition.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: bug-fix -summary: Address a race condition that can occur in Agent diagnostics if log rotation runs while logs are being zipped. -component: elastic-agent -pull_request: https://github.com/elastic/elastic-agent/pull/8215 diff --git a/changelog/fragments/1749110938-update-otel-components-to-v0.125.0.yaml b/changelog/fragments/1749110938-update-otel-components-to-v0.125.0.yaml deleted file mode 100644 index 6863eb6aaec..00000000000 --- a/changelog/fragments/1749110938-update-otel-components-to-v0.125.0.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: Update OTel components to v0.125.0 - -# 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/1749176965-add-cumulativetodeltaprocessor.yaml b/changelog/fragments/1749176965-add-cumulativetodeltaprocessor.yaml deleted file mode 100644 index 6f1275df486..00000000000 --- a/changelog/fragments/1749176965-add-cumulativetodeltaprocessor.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 cumulativetodeltaprocessor 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/1749742685-Use-paths.TempDir-for-diagnostics-actions.yaml b/changelog/fragments/1749742685-Use-paths.TempDir-for-diagnostics-actions.yaml deleted file mode 100644 index 1eee16b3534..00000000000 --- a/changelog/fragments/1749742685-Use-paths.TempDir-for-diagnostics-actions.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: Use paths.TempDir for diagnostics actions - -# 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/elastic/elastic-agent/pull/8472 - -# 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/1749824071-add-apmconfig-apikeyauth-extension.yaml b/changelog/fragments/1749824071-add-apmconfig-apikeyauth-extension.yaml deleted file mode 100644 index 5358eb5b3c4..00000000000 --- a/changelog/fragments/1749824071-add-apmconfig-apikeyauth-extension.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 apmconfig and apikeyauth OTel extensions - -# 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/1749844873-Use-Debian-11-for-linux-arm-to-match-linux-amd64.yaml b/changelog/fragments/1749844873-Use-Debian-11-for-linux-arm-to-match-linux-amd64.yaml deleted file mode 100644 index a0727e01a93..00000000000 --- a/changelog/fragments/1749844873-Use-Debian-11-for-linux-arm-to-match-linux-amd64.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: Use Debian 11 to build linux/arm to match linux/amd64. Upgrades linux/arm64's statically linked glibc from 2.28 to 2.31. - -# 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/elastic/elastic-agent/pull/8497 - -# 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/1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml b/changelog/fragments/1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml deleted file mode 100644 index 6608d633048..00000000000 --- a/changelog/fragments/1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml +++ /dev/null @@ -1,33 +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: relax file ownership check to allow admin re-enrollment on Windows - -# 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: | - On Windows, the agent previously enforced a strict file ownership (SID) check during re-enrollment, which prevented legitimate admin users from re-enrolling the agent if the owner did not match. This PR changes the Windows-specific logic to a no-op, allowing any admin to re-enroll the agent. This restores usability for admin users, but reintroduces the risk that privileged re-enrollment can break unprivileged installs. The Unix-specific ownership check remains unchanged. - -# 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/elastic/elastic-agent/pull/8503 - -# 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/7794 diff --git a/changelog/fragments/1750008201-update-otel-components-to-v0.127.0.yaml b/changelog/fragments/1750008201-update-otel-components-to-v0.127.0.yaml deleted file mode 100644 index 0b90ebdeb88..00000000000 --- a/changelog/fragments/1750008201-update-otel-components-to-v0.127.0.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: Update OTel components to v0.127.0 - -# 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/1750329445-add-bearertokenauth-extension.yaml b/changelog/fragments/1750329445-add-bearertokenauth-extension.yaml deleted file mode 100644 index 29ca95a0dac..00000000000 --- a/changelog/fragments/1750329445-add-bearertokenauth-extension.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 bearertokenauth Otel extension - -# 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/1750349806-elasticsearchexporter-deprecated-config.yaml b/changelog/fragments/1750349806-elasticsearchexporter-deprecated-config.yaml deleted file mode 100644 index 0a43e3d0010..00000000000 --- a/changelog/fragments/1750349806-elasticsearchexporter-deprecated-config.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: Remove deprecated otel elasticsearch exporter config `*_dynamic_index` from code and samples - -# 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/elastic/elastic-agent/pull/8592 - -# 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/1750408426-kube-stack-service-attrs.yaml b/changelog/fragments/1750408426-kube-stack-service-attrs.yaml deleted file mode 100644 index 4ce7224f942..00000000000 --- a/changelog/fragments/1750408426-kube-stack-service-attrs.yaml +++ /dev/null @@ -1,38 +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: Remove resource/k8s processor and use k8sattributes processor for service attributes - -# 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: | - This PR removes the `resource/k8s` processor in honour of the k8sattributes processor that - provides native support for the Service attributes: - https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.127.0/processor/k8sattributesprocessor#configuring-recommended-resource-attributes - - This change is aligned with the respective Semantic Conventions' guidance: - https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#service-attributes - -# 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/elastic/elastic-agent/pull/8599 - -# 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/1750412496-bump-apmconfig-extension.yaml b/changelog/fragments/1750412496-bump-apmconfig-extension.yaml deleted file mode 100644 index c832c92c3eb..00000000000 --- a/changelog/fragments/1750412496-bump-apmconfig-extension.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: upgrade - -# Change summary; a 80ish characters long description of the change. -summary: Bump apmconfig extension to v0.3.0 - -# 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/1750781638-Deprecate-the-elasticinframetrics-processor.yaml b/changelog/fragments/1750781638-Deprecate-the-elasticinframetrics-processor.yaml deleted file mode 100644 index 3036776d613..00000000000 --- a/changelog/fragments/1750781638-Deprecate-the-elasticinframetrics-processor.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: deprecation - -# Change summary; a 80ish characters long description of the change. -summary: Deprecate the elasticinframetrics processor. It will be removed in 9.2.0. - -# 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: "edot" - -# 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/elastic/elastic-agent/pull/8659 - -# 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/1751029489-synth-upgra-node-v20.yaml b/changelog/fragments/1751029489-synth-upgra-node-v20.yaml deleted file mode 100644 index 0e2a83d1728..00000000000 --- a/changelog/fragments/1751029489-synth-upgra-node-v20.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: other - -# Change summary; a 80ish characters long description of the change. -summary: Upgrade Synthetics NodeJS version to latest LTS v20. - -# 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: heartbeat - -# 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/elastic/elastic-agent/pull/8712 - -# 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/1751037802-Stop-logging-that-unprivileged-installations-are-in-beta.yaml b/changelog/fragments/1751037802-Stop-logging-that-unprivileged-installations-are-in-beta.yaml deleted file mode 100644 index 67ffdf7c95f..00000000000 --- a/changelog/fragments/1751037802-Stop-logging-that-unprivileged-installations-are-in-beta.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: Remove incorrect logging that unprivileged installations are in beta. - -# 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: "Unprivileged installations went GA in 8.15.0: https://www.elastic.co/docs/reference/fleet/elastic-agent-unprivileged" - -# 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/elastic/elastic-agent/pull/8715 - -# 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/8689 diff --git a/changelog/fragments/1751317599-edot-collector-include-forwardconnector.yaml b/changelog/fragments/1751317599-edot-collector-include-forwardconnector.yaml deleted file mode 100644 index a92a340735d..00000000000 --- a/changelog/fragments/1751317599-edot-collector-include-forwardconnector.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: Include the forwardconnector as an EDOT collector commponent. - -# 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: https://github.com/open-telemetry/opentelemetry-collector/tree/main/connector/forwardconnector - -# 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/elastic/elastic-agent/pull/8753 - -# 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/1751444462-add_logs_only_motel_config.yaml b/changelog/fragments/1751444462-add_logs_only_motel_config.yaml deleted file mode 100644 index 0c41736ac7a..00000000000 --- a/changelog/fragments/1751444462-add_logs_only_motel_config.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 file logs only mOTEL kube-stack configuration - -# 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/1751455886-correct-log-level-for-standalone-agents.yaml b/changelog/fragments/1751455886-correct-log-level-for-standalone-agents.yaml deleted file mode 100644 index fccd604fdd8..00000000000 --- a/changelog/fragments/1751455886-correct-log-level-for-standalone-agents.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: bug-fix -summary: Ensure standalone Elastic Agent uses log level from configuration instead of persisted state -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/8784 -issue: https://github.com/elastic/elastic-agent/issues/8137 diff --git a/changelog/fragments/1751458785-update-otel-components-to-v0.129.0.yaml b/changelog/fragments/1751458785-update-otel-components-to-v0.129.0.yaml deleted file mode 100644 index 1bf22f930e3..00000000000 --- a/changelog/fragments/1751458785-update-otel-components-to-v0.129.0.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: Update OTel components to v0.129.0 - -# 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/1751536568-update-apmconfig-extension-v0.4.0.yaml b/changelog/fragments/1751536568-update-apmconfig-extension-v0.4.0.yaml deleted file mode 100644 index 2ab0922142e..00000000000 --- a/changelog/fragments/1751536568-update-apmconfig-extension-v0.4.0.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: Update APM Config extension to v0.4.0 - -# 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/1751638649-update-elastictrace-processor-to-v0.7.0.yaml b/changelog/fragments/1751638649-update-elastictrace-processor-to-v0.7.0.yaml deleted file mode 100644 index 11efc5c70c9..00000000000 --- a/changelog/fragments/1751638649-update-elastictrace-processor-to-v0.7.0.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: Update Elastic Trace processor to v0.7.0 - -# 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/1751638799-update-elasticapm-connector-to-v0.4.0.yaml b/changelog/fragments/1751638799-update-elasticapm-connector-to-v0.4.0.yaml deleted file mode 100644 index 3a78ae775be..00000000000 --- a/changelog/fragments/1751638799-update-elasticapm-connector-to-v0.4.0.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: Update Elastic APM connector to v0.4.0 - -# 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/1751639092-update-apikeyauth-extension-to-v0.2.0.yaml b/changelog/fragments/1751639092-update-apikeyauth-extension-to-v0.2.0.yaml deleted file mode 100644 index 75ffc96ee73..00000000000 --- a/changelog/fragments/1751639092-update-apikeyauth-extension-to-v0.2.0.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: Update API Key Auth extension to v0.2.0 - -# 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/1751639206-update-elastic-infra-metrics-processor-to-v0.16.0.yaml b/changelog/fragments/1751639206-update-elastic-infra-metrics-processor-to-v0.16.0.yaml deleted file mode 100644 index c8d3c5eacdb..00000000000 --- a/changelog/fragments/1751639206-update-elastic-infra-metrics-processor-to-v0.16.0.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: Update Elastic Infra Metrics processor to v0.16.0 - -# 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/1751960319-fix-blocking-issues-inside-runtime-communicator.yaml b/changelog/fragments/1751960319-fix-blocking-issues-inside-runtime-communicator.yaml deleted file mode 100644 index 8751505a6c0..00000000000 --- a/changelog/fragments/1751960319-fix-blocking-issues-inside-runtime-communicator.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: bug-fix -summary: Resolve deadlocks in runtime checkin communication -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/8881 -issue: https://github.com/elastic/elastic-agent/issues/7944 diff --git a/changelog/fragments/1752049251-Fixed-SUSE-installation-from-RPM.yaml b/changelog/fragments/1752049251-Fixed-SUSE-installation-from-RPM.yaml deleted file mode 100644 index afa59a65dfc..00000000000 --- a/changelog/fragments/1752049251-Fixed-SUSE-installation-from-RPM.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: Removed init.d support from RPM packages - -# 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/elastic/elastic-agent/pull/8896 - -# 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/8840 From fff113326874febf218ab358a5e2f17939200c34 Mon Sep 17 00:00:00 2001 From: Eric Beahan Date: Mon, 28 Jul 2025 13:10:44 -0500 Subject: [PATCH 2/4] Changelog for 9.1.0 --- changelog/9.1.0.asciidoc | 283 +++++++++ changelog/9.1.0.yaml | 1238 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 1521 insertions(+) create mode 100644 changelog/9.1.0.asciidoc create mode 100644 changelog/9.1.0.yaml diff --git a/changelog/9.1.0.asciidoc b/changelog/9.1.0.asciidoc new file mode 100644 index 00000000000..987e3452102 --- /dev/null +++ b/changelog/9.1.0.asciidoc @@ -0,0 +1,283 @@ +// begin 9.1.0 relnotes + +[[release-notes-9.1.0]] +== 9.1.0 + +Review important information about the 9.1.0 release. + +[discrete] +[[security-updates-9.1.0]] +=== Security updates + + +elastic-agent:: + +* Upgrade To Go 1.22.8. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5731[#https://github.com/elastic/elastic-agent/pull/5731] +* Upgrade To Go 1.24.3. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8109[#https://github.com/elastic/elastic-agent/pull/8109] + +[discrete] +[[breaking-changes-9.1.0]] +=== 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. + +// TODO: add details and impact + +elastic-agent:: + +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/5481]] +.Remove Cloud-Defend From Agent Package. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5481[#https://github.com/elastic/elastic-agent/pull/5481] +[%collapsible] +==== + +==== +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/5536]] +.Remove Default Credentials When Running Elastic Agent In Container Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5536[#https://github.com/elastic/elastic-agent/pull/5536] +[%collapsible] +==== +ELASTICSEARCH_USERNAME and ELASTICSEARCH_PASSWORD now need to be explicitly set when running the agent in container mode +==== +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/5847]] +.Crossbuild-Debian11. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5847[#https://github.com/elastic/elastic-agent/pull/5847] +[%collapsible] +==== +We're dropping support for Debian 10, so no need to crossbuild using the outdated image anymore. This also updates the statically linked glibc from 2.19 to 2.31. +==== +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/6427]] +.Replace Default Ubuntu-Based Images With Ubi-Minimal-Based Ones. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6427[#https://github.com/elastic/elastic-agent/pull/6427] +[%collapsible] +==== + +==== +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/6461/files]] +.Removing --Path.install Option. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6461/files[#https://github.com/elastic/elastic-agent/pull/6461/files] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/2489[#https://github.com/elastic/elastic-agent/issues/2489] +[%collapsible] +==== + +==== +[discrete] +[[breaking-]] +.Changes To Binary Distribution. +[%collapsible] +==== +Default install installs only: + - agentbeat + - endpoint-security + - pf-host-agent +additional flag is added that includes components above and: + - cloudbeat + - apm-server + - fleet-server + - pf-elastic-symbolizer + - pf-elastic-collector + +==== +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/7894]] +.[Otel] Disable Process Scraper Of Hostmetrics Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7894[#https://github.com/elastic/elastic-agent/pull/7894] +[%collapsible] +==== +The process scraper collects metrics for all available processes of a host without an easy way to limit +this to only report top N process for example. This results in quite big amount of timeseries. +Since this is not quite critical for any of the available UIs or dashboards we decide to disable +it temporarily until we find a better solution. Users that specifically need these metrics +can also enable it back manually. +Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/39423. + +==== + + + +[discrete] +[[deprecations-9.1.0]] +=== Deprecations + +The following functionality is deprecated in 9.1.0, and will be removed in +9.1.0. Deprecated functionality does not have an immediate impact on your +application, but we strongly recommend you make the necessary updates after you +upgrade to 9.1.0. + + +edot:: + +* Deprecate The Elasticinframetrics Processor. It Will Be Removed In 9.2.0. {edot-pull}https://github.com/elastic/elastic-agent/pull/8659[#https://github.com/elastic/elastic-agent/pull/8659] { $k | section}}::$k }}:: + +[discrete] +[[new-features-9.1.0]] +=== New features + +The 9.1.0 release adds the following new and notable features. + + + + +* Added Support For Pre-Existing Active Directory User For Unprivileged Mode. {-issue}https://github.com/elastic/elastic-agent/issues/4585[#https://github.com/elastic/elastic-agent/issues/4585] ++ +User can specify custom pre-existing user for running unprivileged mode. This user will be given permissions to log on as a service. +* Add Filesource Provider. {-pull}https://github.com/elastic/elastic-agent/pull/6587[#https://github.com/elastic/elastic-agent/pull/6587] {-issue}https://github.com/elastic/elastic-agent/issues/6362[#https://github.com/elastic/elastic-agent/issues/6362] ++ +filesource provider watches for changes of the files and updates the values of the variables +when the content of the file changes. + +* Add --Id And --Replace-Token To Enrollment. {-pull}https://github.com/elastic/elastic-agent/pull/6498[#https://github.com/elastic/elastic-agent/pull/6498] {-issue}https://github.com/elastic/elastic-agent/issues/6361[#https://github.com/elastic/elastic-agent/issues/6361] ++ +Add support for --id and --replace-token to the install and enroll command. Add support for ELASTIC_AGENT_ID +and FLEET_REPLACE_TOKEN to the container support the same behavior as the enroll command. Allows the ability to +define a specific ID to use for the Elastic Agent when enrolling into Fleet. The replace-token defines the token +that must be used to re-enroll an Elastic Agent with the same ID as a replacement of the previous Elastic Agent. + +elastic-agent:: + +* Upgrade-To-Go-1.24.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5309[#https://github.com/elastic/elastic-agent/pull/5309] +* Add Ability To Run Elastic Distribution Of Otel Collector At The Same Time As Other Inputs. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5767[#https://github.com/elastic/elastic-agent/pull/5767] +* Add Os_family, Os_platform And Os_version To Host Provider. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5941[#https://github.com/elastic/elastic-agent/pull/5941] {elastic-agent-issue}https://github.com/elastic/integrations/issues/10797[#https://github.com/elastic/integrations/issues/10797] +* Add Geoip Processor To Edot Collector. +* Add Metricbeat Otel Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6182[#https://github.com/elastic/elastic-agent/pull/6182] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6138[#https://github.com/elastic/elastic-agent/issues/6138] +* Add Opentelemetry Routing Connector To Edot Collector. +* Add Loadbalancing Exporter To Edot Collector. +* Removes `List` From Kibanafetchtoken In Favor Of `Items` As The Former Is Deprecated And Will Be Removed From The Api Response. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6437[#https://github.com/elastic/elastic-agent/pull/6437] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6023[#https://github.com/elastic/elastic-agent/issues/6023] +* Add Gateway Collector In Helm Kube-Stack Deployment. +* Add `Components` Command For `Otel` Mode. +* Add Receivercreator And K8sobserver To Edot Collector. +* Use A Random Free Port For Sub-Process Communication In Containers By Default. Avoids Port Collisions When Using Host Networking In Kubernetes. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6585[#https://github.com/elastic/elastic-agent/pull/6585] +* Add Kafkaexporter And Kafkareceiver To Edot Collector. {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6562[#https://github.com/elastic/elastic-agent/issues/6562] +* Add Jmxreceiver To Edot Collector. +* Add Nopreceiver To Edot Collector. +* Add Context Variable Support To Outputs. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6602[#https://github.com/elastic/elastic-agent/pull/6602] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6376[#https://github.com/elastic/elastic-agent/issues/6376] ++ +Adds support for using context variable providers in the outputs section of a policy. Includes fallback support +to reference env provider when no provider prefix is provided in the variable. + +* Add Nginx Receiver And Redis Receiver Otel Components. +* Add Motel Sample Configurations. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6630[#https://github.com/elastic/elastic-agent/pull/6630] +* Set Replicas For Gateway Collector. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7011[#https://github.com/elastic/elastic-agent/pull/7011] +* Add Nopexporter To Edot Collector. +* Adds A New Configuration Setting, `Agent.upgrade.rollback.window`. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8065[#https://github.com/elastic/elastic-agent/pull/8065] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6881[#https://github.com/elastic/elastic-agent/issues/6881] ++ +The value of the `agent.upgrade.rollback.window` setting determines the period after upgrading +Elastic Agent when a rollback to the previous version can be triggered. This is an optional +setting, with a default value of `168h` (7 days). The value can be any string that is parseable +by https://pkg.go.dev/time#ParseDuration. + +* Add Cumulativetodeltaprocessor To Edot Collector. +* Add Apmconfig And Apikeyauth Otel Extensions. +* Add Bearertokenauth Otel Extension. +* Remove Resource/K8s Processor And Use K8sattributes Processor For Service Attributes. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8599[#https://github.com/elastic/elastic-agent/pull/8599] ++ +This PR removes the `resource/k8s` processor in honour of the k8sattributes processor that +provides native support for the Service attributes: +https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.127.0/processor/k8sattributesprocessor#configuring-recommended-resource-attributes + +This change is aligned with the respective Semantic Conventions' guidance: +https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#service-attributes + +* Add File Logs Only Motel Kube-Stack Configuration. +elastic-agent,otel:: + +* Enable Persistence In The Configuration Provided With Our Otel Collector Distribution. {elastic-agent,otel-pull}https://github.com/elastic/elastic-agent/pull/5549[#https://github.com/elastic/elastic-agent/pull/5549] + + +[discrete] +[[enhancements-9.1.0]] +=== Enhancements + + +elastic-agent:: + +* Support Elasticsearch_api_key Environment Variable When Running In Container Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5536[#https://github.com/elastic/elastic-agent/pull/5536] +* Add Filebeat Otel Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5833[#https://github.com/elastic/elastic-agent/pull/5833] +* Detect And Fail-Early Cli Upgrades If Agent Is Fleet-Managed. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5864[#https://github.com/elastic/elastic-agent/pull/5864] +* Removed Endpoint Security From Linux Containers. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6016[#https://github.com/elastic/elastic-agent/pull/6016] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5495[#https://github.com/elastic/elastic-agent/issues/5495] +* Re-Enable Otel Subcommand On Windows. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6068[#https://github.com/elastic/elastic-agent/pull/6068] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/4976[#https://github.com/elastic/elastic-agent/issues/4976] +* Update Otel Components To V0.114.0. +* Elastic Agent Returns An Actionable Error Message When A The Use Trying To Execute The Enroll Command Is Not The Same As The Onwer Of The Elastic-Agent Program Files. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6144[#https://github.com/elastic/elastic-agent/pull/6144] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/4889[#https://github.com/elastic/elastic-agent/issues/4889] +* Only Run Providers Referenced In The Policy. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6169[#https://github.com/elastic/elastic-agent/pull/6169] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3609[#https://github.com/elastic/elastic-agent/issues/3609] +* Add A Flag To Skip Audit/Unenroll Call To Fleet Server During Uninstall. +* Update Otel Components To V0.115.0. +* Redact Common Secrets Like Api Keys And Passwords In The Output From `Inspect` Command. +* Prevent Leaking Secrets When Logging The Component Model. +* Embed Hints-Based Inputs In The Elastic Agent Container Image. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6381[#https://github.com/elastic/elastic-agent/pull/6381] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5661[#https://github.com/elastic/elastic-agent/issues/5661] +* Update Otel Components To V0.116.0. +* Windows Add Event Logging To Install, Uninstall, Enroll Failures. {elastic-agent-pull}https://github.com/elastic/elastic-agent/6410[#https://github.com/elastic/elastic-agent/6410] {elastic-agent-issue}https://github.com/elastic/elastic-agent/6338[#https://github.com/elastic/elastic-agent/6338] +* Added Logger To Print The Status And Code When Enrollment Call To Fleet Failed. {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6287[#https://github.com/elastic/elastic-agent/issues/6287] +* Update Otel Components To V0.117.0. +* Updated The Fleet Gateway So That When The Number Of Unauthorized Fleet Responses Exceeds The Set Limit, Instead Of Unenrolling, The Gateway Starts Checking In Less Frequently. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6619[#https://github.com/elastic/elastic-agent/pull/6619] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5428[#https://github.com/elastic/elastic-agent/issues/5428] +* Update Otel Components To V0.119.0. +* Improve Kubernetes_secrets Provider Secret Logging. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6841[#https://github.com/elastic/elastic-agent/pull/6841] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6187[#https://github.com/elastic/elastic-agent/issues/6187] +* Allow Upgrading Deb Or Rpm Agents When Using Elastic Defend With Tamper Protection. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6907[#https://github.com/elastic/elastic-agent/pull/6907] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6394[#https://github.com/elastic/elastic-agent/issues/6394] +* Add Apikey Prefix To Motel Host Configurations. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7063[#https://github.com/elastic/elastic-agent/pull/7063] +* Add Elastic.agent.fips To Local_metadata. {elastic-agent-issue}https://github.com/elastic/elastic-agent/pull/7112[#https://github.com/elastic/elastic-agent/pull/7112] +* Validate Pbkdf2 Settings When In Fips Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7187[#https://github.com/elastic/elastic-agent/pull/7187] +* Fips-Capable Agent File Vault. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7360[#https://github.com/elastic/elastic-agent/pull/7360] +* With This Change Fips-Capable Agents Will Only Be Able To Upgrade To Other Fips-Capable Agents. This Change Also Restricts Non-Fips To Fips Upgrades As Well. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7312[#https://github.com/elastic/elastic-agent/pull/7312] {elastic-agent-issue}https://github.com/elastic/ingest-dev/issues/4811[#https://github.com/elastic/ingest-dev/issues/4811] +* Updated The Error Messages Returned For Fips Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7453[#https://github.com/elastic/elastic-agent/pull/7453] +* Update Otel Components To V0.121.0. +* Update Otel Components To V0.122.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7725[#https://github.com/elastic/elastic-agent/pull/7725] +* Update Otel Components To V0.123.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7996[#https://github.com/elastic/elastic-agent/pull/7996] +* Retry Enrollment Requests On Any Error. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8056[#https://github.com/elastic/elastic-agent/pull/8056] +* Update Otel Components To V0.125.0. +* Update Otel Components To V0.127.0. +* Remove Deprecated Otel Elasticsearch Exporter Config `*_Dynamic_index` From Code And Samples. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8592[#https://github.com/elastic/elastic-agent/pull/8592] +* Include The Forwardconnector As An Edot Collector Commponent. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8753[#https://github.com/elastic/elastic-agent/pull/8753] +* Update Otel Components To V0.129.0. +* Update Apm Config Extension To V0.4.0. +* Update Elastic Trace Processor To V0.7.0. +* Update Elastic Apm Connector To V0.4.0. +* Update Api Key Auth Extension To V0.2.0. +* Update Elastic Infra Metrics Processor To V0.16.0. + + +[discrete] +[[upgrades-9.1.0]] +=== Upgrades + + +elastic-agent:: + +* Bump Apmconfig Extension To V0.3.0. + + +[discrete] +[[bug-fixes-9.1.0]] +=== Bug fixes + + + + +* Notify Fleet Of Uninstall On Windows. {-pull}https://github.com/elastic/elastic-agent/pull/6257[#https://github.com/elastic/elastic-agent/pull/6257] {-issue}https://github.com/elastic/elastic-agent/issues/5952[#https://github.com/elastic/elastic-agent/issues/5952] +* Fix Deadlock In Otelmanager. {-pull}https://github.com/elastic/elastic-agent/pull/6927[#https://github.com/elastic/elastic-agent/pull/6927] +elastic-agent:: + +* Prevent Installing Elastic Defend On Non Native Architecture. +* Added Retries For Requesting Download Verifiers When Upgrading The Agent. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6276[#https://github.com/elastic/elastic-agent/pull/6276] +* The Install Command Is Updated So That If A User Installs An Agent, While There Is Already An Agent, Using The `--Force` Flag Replaces The Correct One. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6559[#https://github.com/elastic/elastic-agent/pull/6559] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5595[#https://github.com/elastic/elastic-agent/issues/5595] +* Fix Enrollment For Containerised Agent When Enrollment Token Changes Or The Agent Is Unenrolled. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6568[#https://github.com/elastic/elastic-agent/pull/6568] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3586[#https://github.com/elastic/elastic-agent/issues/3586] +* Fix Logical Race Conditions In Kubernetes_secrets Provider. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6623[#https://github.com/elastic/elastic-agent/pull/6623] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6340[#https://github.com/elastic/elastic-agent/issues/6340] +* Fix Tsdb Version_conflict_engine_exception Caused By Incorrect Kube-Stack Helm Values. +* Support Ipv6 Host In Agent Monitoring Http Config. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7073[#https://github.com/elastic/elastic-agent/pull/7073] +* Fix Elasticsearch Exporter Configuration In Kube-Stack Values. +* Correctly Handle Sending Signal To Child Process. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7738[#https://github.com/elastic/elastic-agent/pull/7738] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6875[#https://github.com/elastic/elastic-agent/issues/6875] +* Fix Managed Otlp Helm Config To Use Current Image Repo. +* Ship Journalctl In The Elastic-Agent, Elastic-Agent-Complete, And +Elastic-Otel-Collector Docker Images To Enable Reading Journald +Logs. Journalctl Is Not Present On *-Slim And All Wolfi Images. +. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7995[#https://github.com/elastic/elastic-agent/pull/7995] {elastic-agent-issue}https://github.com/elastic/beats/issues/44040[#https://github.com/elastic/beats/issues/44040] +* Preserve Agent Run State On Deb And Rpm Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7999[#https://github.com/elastic/elastic-agent/pull/7999] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3832[#https://github.com/elastic/elastic-agent/issues/3832] +* Use --Header From Enrollment When Communicating With Fleet Server. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8071[#https://github.com/elastic/elastic-agent/pull/8071] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6823[#https://github.com/elastic/elastic-agent/issues/6823] +* Address A Race Condition That Can Occur In Agent Diagnostics If Log Rotation Runs While Logs Are Being Zipped. +* Use Paths.tempdir For Diagnostics Actions. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8472[#https://github.com/elastic/elastic-agent/pull/8472] +* Use Debian 11 To Build Linux/Arm To Match Linux/Amd64. Upgrades Linux/Arm64's Statically Linked Glibc From 2.28 To 2.31. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8497[#https://github.com/elastic/elastic-agent/pull/8497] +* Relax File Ownership Check To Allow Admin Re-Enrollment On Windows. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8503[#https://github.com/elastic/elastic-agent/pull/8503] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/7794[#https://github.com/elastic/elastic-agent/issues/7794] +* Remove Incorrect Logging That Unprivileged Installations Are In Beta. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8715[#https://github.com/elastic/elastic-agent/pull/8715] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8689[#https://github.com/elastic/elastic-agent/issues/8689] +* Ensure Standalone Elastic Agent Uses Log Level From Configuration Instead Of Persisted State. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8784[#https://github.com/elastic/elastic-agent/pull/8784] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8137[#https://github.com/elastic/elastic-agent/issues/8137] +* Resolve Deadlocks In Runtime Checkin Communication. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8881[#https://github.com/elastic/elastic-agent/pull/8881] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/7944[#https://github.com/elastic/elastic-agent/issues/7944] +* Removed Init.d Support From Rpm Packages. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8896[#https://github.com/elastic/elastic-agent/pull/8896] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8840[#https://github.com/elastic/elastic-agent/issues/8840] + +// end 9.1.0 relnotes diff --git a/changelog/9.1.0.yaml b/changelog/9.1.0.yaml new file mode 100644 index 00000000000..4b7f5b9f704 --- /dev/null +++ b/changelog/9.1.0.yaml @@ -0,0 +1,1238 @@ +version: 9.1.0 +entries: + - kind: feature + summary: Upgrade-to-Go-1.24.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5309 + issue: [] + timestamp: 1723829102 + file: + name: 1723829102-Upgrade-to-Go-1.23.0.yaml + checksum: 85618dbc474cb2a75c33ad9eb31600a3b07b230a + - kind: breaking-change + summary: Remove cloud-defend from agent package + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5481 + issue: [] + timestamp: 1725913991 + file: + name: 1725913991-remove-cloud-defend.yaml + checksum: 5bc3b5e31f850ce19da3ff2bdd0f6710a15efb06 + - kind: breaking-change + summary: Remove default credentials when running Elastic Agent in container mode + description: ELASTICSEARCH_USERNAME and ELASTICSEARCH_PASSWORD now need to be explicitly set when running the agent in container mode + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5536 + issue: [] + timestamp: 1726144746 + file: + name: 1726144746-container-default-credentials.yaml + checksum: 787ea64973b0a62effa8d92fc308bf95ad084d9d + - kind: enhancement + summary: Support ELASTICSEARCH_API_KEY environment variable when running in container mode + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5536 + issue: [] + timestamp: 1726145045 + file: + name: 1726145045-container-api-key.yaml + checksum: 80738c5524291194c91c457bdfb5baf80a339522 + - kind: feature + summary: Enable persistence in the configuration provided with our OTel Collector distribution. + description: "" + component: elastic-agent,otel + pr: + - https://github.com/elastic/elastic-agent/pull/5549 + issue: [] + timestamp: 1726572104 + file: + name: 1726572104-enable-persistence-by-default.yaml + checksum: 9f79bc53034a5d6e7c00f14dbb90682bb2331328 + - kind: security + summary: Upgrade to Go 1.22.8. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5731 + issue: [] + timestamp: 1728332120 + file: + name: 1728332120-Upgrade-to-Go-1.22.8..yaml + checksum: 959431da51ad449f61effe2d131c8ab87139e731 + - kind: feature + summary: Add ability to run Elastic Distribution of OTel Collector at the same time as other inputs + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5767 + issue: [] + timestamp: 1729011748 + file: + name: 1729011748-Add-EDOT-hybrid-mode.yaml + checksum: 83f6f4cb37cb776770ca9ff99b39228b9529df54 + - kind: enhancement + summary: Add filebeat otel receiver + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5833 + issue: [] + timestamp: 1729630977 + file: + name: 1729630977-Add-filebeat-otel-receiver.yaml + checksum: 0e5e55864891cc5896a90a015decd87e8f463556 + - kind: breaking-change + summary: crossbuild-debian11 + description: We're dropping support for Debian 10, so no need to crossbuild using the outdated image anymore. This also updates the statically linked glibc from 2.19 to 2.31. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5847 + issue: [] + timestamp: 1729750939 + file: + name: 1729750939-crossbuild-debian11.yaml + checksum: 4972f2ef7a2315f39713345eb471a00a0573eff8 + - kind: enhancement + summary: Detect and fail-early cli upgrades if agent is fleet-managed + description: This change brings restrictions on the upgrade cli command. If an agent is fleet-managed and is running in unprivileged mode, users won't be able to upgrade the agent using the cli. If an agent is fleet-managed and is running privileged, users will only be able to upgrade the agent using the cli if they provide --force flag. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5864 + issue: [] + timestamp: 1729971565 + file: + name: 1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml + checksum: 9e787dd2741fe58524f9736d969f35a0b1dcbecb + - kind: feature + summary: Add os_family, os_platform and os_version to host provider + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/5941 + issue: + - https://github.com/elastic/integrations/issues/10797 + timestamp: 1730986549 + file: + name: 1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.yaml + checksum: f2dabf4cc393c6a4bd1c6e30d8fdd6f8ba71fc19 + - kind: feature + summary: Added support for pre-existing Active Directory user for unprivileged mode + description: User can specify custom pre-existing user for running unprivileged mode. This user will be given permissions to log on as a service. + component: "" + pr: [] + issue: + - https://github.com/elastic/elastic-agent/issues/4585 + timestamp: 1731314919 + file: + name: 1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.yaml + checksum: 1bba4dcbe7d1a12549a958c7849900a3018102c1 + - kind: enhancement + summary: removed endpoint security from linux containers + description: Removed elastic endpoint security from linux containers as it has a dependency on systemd. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6016 + issue: + - https://github.com/elastic/elastic-agent/issues/5495 + timestamp: 1731517501 + file: + name: 1731517501-removed-endpoint-security-from-linux-containers.yaml + checksum: 73ce73dcbe55f9a094386af3ce0db5d13327d63e + - kind: enhancement + summary: re-enable otel subcommand on Windows + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6068 + issue: + - https://github.com/elastic/elastic-agent/issues/4976 + timestamp: 1731962301 + file: + name: 1731962301-re-enable-otel-subcommand-on-Windows.yaml + checksum: ea1fe69816ff322cb2cc91ccf32812a4cb5b503c + - kind: bug-fix + summary: Prevent installing Elastic Defend on non native architecture + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1732110636 + file: + name: 1732110636-elastic-defend-cannot-run-in-emulation.yaml + checksum: cc811ca8793718da37ee77b8dfdcc38bf28ed8eb + - kind: enhancement + summary: Update OTel components to v0.114.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1732187698 + file: + name: 1732187698-update-otel-v0.114.0.yaml + checksum: 34dc5f9c30bbfd353a2fb037ec36eb36afefb9c6 + - kind: enhancement + summary: Elastic agent returns an actionable error message when a the use trying to execute the enroll command is not the same as the onwer of the elastic-agent program files + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6144 + issue: + - https://github.com/elastic/elastic-agent/issues/4889 + timestamp: 1732656422 + file: + name: 1732656422-add-actionable-error-message-for-enroll-command.yaml + checksum: 26a631d17865361a1dd4c8fee8b14c27e7141ef7 + - kind: feature + summary: add GeoIP processor to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1732809895 + file: + name: 1732809895-add-GeoIP-processor-to-EDOT-collector.yaml + checksum: 277f35b0578e38c852c8b70106d2be39d6bec337 + - kind: enhancement + summary: Only run providers referenced in the policy + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6169 + issue: + - https://github.com/elastic/elastic-agent/issues/3609 + timestamp: 1732840106 + file: + name: 1732840106-Only-run-providers-referenced-in-the-policy.yaml + checksum: 0cc32a70c3ce3907a4a97032e870d5ab2f558b3c + - kind: feature + summary: add metricbeat otel receiver + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6182 + issue: + - https://github.com/elastic/elastic-agent/issues/6138 + timestamp: 1733156311 + file: + name: 1733156311-add-metricbeat-otel-receiver.yaml + checksum: b288610f75f9885b18152142766d7f3ef7da32b6 + - kind: enhancement + summary: Add a flag to skip audit/unenroll call to fleet server during uninstall + description: This change adds a flag to skip audit/unenroll call to fleet server. While uninstalling elastic-agent it tries to notify fleet server about the uninstallation. But in somecases users might know that the fleet server is unreachable and this notification logs multiple failures continuously. Adding this flag skips this call. + component: elastic-agent + pr: [] + issue: [] + timestamp: 1733248787 + file: + name: 1733248787-flag-to-skip-fleet-audit.yaml + checksum: 90feaadcd5767184283b24e3d939e733974d8dc4 + - kind: feature + summary: Add OpenTelemetry Routing connector to EDOT Collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1733317274 + file: + name: 1733317274-add-routing-connector-to-EDOT-collector.yaml + checksum: 97ad4a46f22735875d557534e2c11d4874e3ced4 + - kind: enhancement + summary: Update OTel components to v0.115.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1733390040 + file: + name: 1733390040-update-otel-0.115.0.yaml + checksum: a5e553950b636961aa866fabd996cc98cf4d674f + - kind: enhancement + summary: Redact common secrets like API keys and passwords in the output from `inspect` command + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1733397457 + file: + name: 1733397457-redact-common-secrets-in-inspect-output.yaml + checksum: 3a6f322345d0be9b1b7babcd283360461097d9f4 + - kind: bug-fix + summary: Notify Fleet of uninstall on Windows + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/6257 + issue: + - https://github.com/elastic/elastic-agent/issues/5952 + timestamp: 1733768621 + file: + name: 1733768621-Notify-Fleet-of-uninstall-on-Windows.yaml + checksum: 2261f729d790b28259c486904351e809fe15ddd3 + - kind: bug-fix + summary: added retries for requesting download verifiers when upgrading the agent + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6276 + issue: [] + timestamp: 1733936340 + file: + name: 1733936340-add-retries-for-download-upgrade-verifiers.yaml + checksum: 4ff5442cc287002e52df7244387e7ef464ee2ffc + - kind: feature + summary: add loadbalancing exporter to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1734023789 + file: + name: 1734023789-add-loadbalancing-exporter-to-EDOT-collector.yaml + checksum: f94fb4193a2f051b82ff70ce5ffa738df36cdb17 + - kind: enhancement + summary: Prevent leaking secrets when logging the component model + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1734098868 + file: + name: 1734098868-prevent-leaking-secrets-when-logging-component-model.yaml + checksum: f97e506ed1e434803b4f98914526b461d013f414 + - kind: enhancement + summary: Embed hints-based inputs in the Elastic Agent container image. + description: This change includes the addition of hints-based inputs directly within the Elastic Agent container image, enabling streamlined configurations for input discovery when deployed in containerized environments. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6381 + issue: + - https://github.com/elastic/elastic-agent/issues/5661 + timestamp: 1734512365 + file: + name: 1734512365-embed-hints-inputs-in-agent-container-image.yaml + checksum: 377396eb3d0baf5ee407947ab72eedfe50ff5c37 + - kind: enhancement + summary: Update OTel components to v0.116.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1734525166 + file: + name: 1734525166-update-otel-v0.116.0.yaml + checksum: 60cb22ef685dfcbf9ef1a97d6d64e40d5eca45c3 + - kind: enhancement + summary: Windows add Event Logging to install, uninstall, enroll failures + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/6410 + issue: + - https://github.com/elastic/elastic-agent/6338 + timestamp: 1734626964 + file: + name: 1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.yaml + checksum: e9bafab97ec550ab78494e4f10f5784cc1d80a39 + - kind: breaking-change + summary: Replace default Ubuntu-based images with UBI-minimal-based ones + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6427 + issue: [] + timestamp: 1734959878 + file: + name: 1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.yaml + checksum: b8ab6a7dbab04b70007a37fb11224f10c4c7e943 + - kind: feature + summary: removes `list` from kibanaFetchToken in favor of `items` as the former is deprecated and will be removed from the api response + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6437 + issue: + - https://github.com/elastic/elastic-agent/issues/6023 + timestamp: 1735137195 + file: + name: 1735137195-remove-deprecated-list-in-favor-of-items.yaml + checksum: 23a9ecf8dad6f29e58581a41e9b8b5ee348c5cba + - kind: feature + summary: add gateway collector in Helm kube-stack deployment + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1735306293 + file: + name: 1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.yaml + checksum: 6ca30d0b19e24fa27872fcd292d10fc31abbb30a + - kind: breaking-change + summary: Removing --path.install option + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6461/files + issue: + - https://github.com/elastic/elastic-agent/issues/2489 + timestamp: 1735664420 + file: + name: 1735664420-remove-deprecated-path-install-cli-flag.yaml + checksum: ceedae40882bfee7db7f8eb0c0b1e8fdd4290638 + - kind: enhancement + summary: Added logger to print the status and code when enrollment call to fleet failed. + description: "" + component: elastic-agent + pr: [] + issue: + - https://github.com/elastic/elastic-agent/issues/6287 + timestamp: 1736002257 + file: + name: 1736002257-log-fleet-enroll-failure-status-code.yaml + checksum: 725fe14f2e5e6a361b8ce21c44ecb37c25c6b4ac + - kind: enhancement + summary: Update OTel components to v0.117.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1736417404 + file: + name: 1736417404-update-otel-v0.117.0.yaml + checksum: 391d8bb42bc60ded03da5d51c579e67baf29ae91 + - kind: feature + summary: Add `components` command for `otel` mode. + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1737106864 + file: + name: 1737106864-add_otel_components_cmd.yaml + checksum: ed1b96a2a42183ce554618f93d199a28a33407d4 + - kind: breaking-change + summary: Changes to binary distribution + description: | + Default install installs only: + - agentbeat + - endpoint-security + - pf-host-agent + additional flag is added that includes components above and: + - cloudbeat + - apm-server + - fleet-server + - pf-elastic-symbolizer + - pf-elastic-collector + component: elastic-agent + pr: [] + issue: [] + timestamp: 1737131552 + file: + name: 1737131552-Changes-to-binary-distribution.yaml + checksum: 2e5094fc0897c99c63089c7a64294197a2772633 + - kind: feature + summary: Add receivercreator and k8sobserver to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1737462864 + file: + name: 1737462864-add_k8s_otel_comps.yaml + checksum: 965a483f6d19b83f62b49e0b29dc00f7720baf20 + - kind: bug-fix + summary: The install command is updated so that if a user installs an agent, while there is already an agent, using the `--force` flag replaces the correct one. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6559 + issue: + - https://github.com/elastic/elastic-agent/issues/5595 + timestamp: 1737473147 + file: + name: 1737473147-force-install-replaces-correct-agent.yaml + checksum: b859983d69d2c1bf215fa0b3448cb49ee695e866 + - kind: bug-fix + summary: Fix enrollment for containerised agent when enrollment token changes or the agent is unenrolled + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6568 + issue: + - https://github.com/elastic/elastic-agent/issues/3586 + timestamp: 1737552345 + file: + name: 1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.yaml + checksum: 271f8551f709ec1e7be7e175c792a48a897cf6cc + - kind: feature + summary: Use a random free port for sub-process communication in containers by default. Avoids port collisions when using host networking in Kubernetes. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6585 + issue: [] + timestamp: 1737657890 + file: + name: 1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.yaml + checksum: d8fe375db50cd5643eb921a0e4ec4e541040b95b + - kind: feature + summary: Add filesource provider + description: | + filesource provider watches for changes of the files and updates the values of the variables + when the content of the file changes. + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/6587 + issue: + - https://github.com/elastic/elastic-agent/issues/6362 + timestamp: 1737666699 + file: + name: 1737666699-Add-filesource-provider.yaml + checksum: 7f858f76eadbfb558d861f03bc49c088b46e02e1 + - kind: feature + summary: add kafkaexporter and kafkareceiver to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: + - https://github.com/elastic/elastic-agent/issues/6562 + timestamp: 1737717648 + file: + name: 1737717648-add-kafkaexporter-otel-collector.yaml + checksum: 62a4f53c8d07652832ca7ffb7fb0abac8a9b9c19 + - kind: feature + summary: add jmxreceiver to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1737749181 + file: + name: 1737749181-add-jmxreceiver-otel-collector.yaml + checksum: b5ba5a564aa217b8c827b74cc19941690de56312 + - kind: feature + summary: add nopreceiver to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1737750331 + file: + name: 1737750331-add-nopreceiver-otel-collector.yaml + checksum: 5658543bbbb08bf6b4b46e5cebe51f51c1f998aa + - kind: feature + summary: Add context variable support to outputs + description: | + Adds support for using context variable providers in the outputs section of a policy. Includes fallback support + to reference env provider when no provider prefix is provided in the variable. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6602 + issue: + - https://github.com/elastic/elastic-agent/issues/6376 + timestamp: 1737816507 + file: + name: 1737816507-Add-context-variable-support-to-outputs.yaml + checksum: a48fcb465af0ff61da95e7833f324f297457c3a2 + - kind: bug-fix + summary: Fix logical race conditions in kubernetes_secrets provider + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6623 + issue: + - https://github.com/elastic/elastic-agent/issues/6340 + timestamp: 1738139927 + file: + name: 1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.yaml + checksum: 4ab7092ac0cdc741dfb2d9eb8e309bcf9e10916a + - kind: feature + summary: Add Nginx receiver and Redis receiver OTel components + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1738160406 + file: + name: 1738160406-add_redis_nginx_otel_comps.yaml + checksum: f15594711ea1346dd4e5322addec37903ce18bc2 + - kind: enhancement + summary: Updated the fleet gateway so that when the number of unauthorized fleet responses exceeds the set limit, instead of unenrolling, the gateway starts checking in less frequently. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6619 + issue: + - https://github.com/elastic/elastic-agent/issues/5428 + timestamp: 1738199968 + file: + name: 1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml + checksum: f3c25d66824668cdb1a227fa4e4fd49decfa51a2 + - kind: enhancement + summary: Update OTel components to v0.119.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1738752554 + file: + name: 1738752554-update-otel-v0.119.0.yaml + checksum: acf16fd9e6005926f4949b78717daae9648b837e + - kind: feature + summary: Add --id and --replace-token to enrollment + description: | + Add support for --id and --replace-token to the install and enroll command. Add support for ELASTIC_AGENT_ID + and FLEET_REPLACE_TOKEN to the container support the same behavior as the enroll command. Allows the ability to + define a specific ID to use for the Elastic Agent when enrolling into Fleet. The replace-token defines the token + that must be used to re-enroll an Elastic Agent with the same ID as a replacement of the previous Elastic Agent. + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/6498 + issue: + - https://github.com/elastic/elastic-agent/issues/6361 + timestamp: 1738784301 + file: + name: 1738784301-Add-id-and-replace-token-to-enrollment.yaml + checksum: db7f63d59e142273afd4a884e2cf7a60a9661187 + - kind: enhancement + summary: Improve kubernetes_secrets provider secret logging + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6841 + issue: + - https://github.com/elastic/elastic-agent/issues/6187 + timestamp: 1739437836 + file: + name: 1739437836-Improve-kubernetes_secrets-provider-secret-logging.yaml + checksum: 0c4b850fae555d18f7a8ba5292f668a28483eaf2 + - kind: feature + summary: add MOtel sample configurations + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6630 + issue: [] + timestamp: 1739544282 + file: + name: 1739544282-add-MOtel-sample-configurations.yaml + checksum: 06334af7feea3aec65ceed7678a960567525869c + - kind: bug-fix + summary: Fix deadlock in OTelManager + description: | + Fixes a deadlock case in the OTelManager where an Update can occur while an error is also being reported + which causes the communication with the OTelManager to hit a deadlock. + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/6927 + issue: [] + timestamp: 1739981369 + file: + name: 1739981369-Fix-deadlock-in-OTelManager.yaml + checksum: 333d2fd898e8b4b3f5108f270562f41554bb974a + - kind: bug-fix + summary: Fix TSDB version_conflict_engine_exception caused by incorrect kube-stack Helm values + description: Setting non-zero send_batch_max_size for metrics risks TSDB version_conflict_engine_exception as it causes metrics grouping in es exporter to not work properly. + component: elastic-agent + pr: [] + issue: [] + timestamp: 1740054191 + file: + name: 1740054191-kube-stack-helm-chart-metrics-batch.yaml + checksum: bd3f5c4ea20a4714a84dca8e9c8875c57c53368d + - kind: enhancement + summary: Allow upgrading deb or rpm agents when using Elastic Defend with tamper protection. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/6907 + issue: + - https://github.com/elastic/elastic-agent/issues/6394 + timestamp: 1740166208 + file: + name: 1740166208-allow-deb-rpm-upgrade-with-tamper-protected-endpoint.yaml + checksum: e1124b779230d456de615b055b3d2c2f2ead20e1 + - kind: feature + summary: set replicas for gateway collector + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7011 + issue: [] + timestamp: 1740492672 + file: + name: 1740492672-set-replicas-for-gateway-collector.yaml + checksum: 4fbd8a8622214c18b656e9ecab4034a17d21535d + - kind: enhancement + summary: add ApiKey prefix to MOTel host configurations + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7063 + issue: [] + timestamp: 1740674973 + file: + name: 1740674973-add-ApiKey-prefix-to-MOTel-host-configurations.yaml + checksum: 23aaa12620e5149b642235c310fbf957682d7a7d + - kind: bug-fix + summary: support ipv6 host in agent monitoring http config + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7073 + issue: [] + timestamp: 1740713597 + file: + name: 1740713597-support-agent-monitoring-ipv6.yaml + checksum: b0b76e19a1b8637eb247611ad302d47eab9db6bc + - kind: enhancement + summary: Add elastic.agent.fips to local_metadata + description: | + Add elastic.agent.fips (bool) attribute to local_metadata sent with enroll and checkin requests. + The value of this attribute indicates if the agent is a FIPS-capable distribution. + component: elastic-agent + pr: [] + issue: + - https://github.com/elastic/elastic-agent/pull/7112 + timestamp: 1740773781 + file: + name: 1740773781-Add-elastic.agent.fips-to-local_metadata.yaml + checksum: 7700361126e87b03fee0a8eb1e87ab40a9e8b28b + - kind: enhancement + summary: Validate pbkdf2 settings when in FIPS mode + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7187 + issue: [] + timestamp: 1741122475 + file: + name: 1741122475-Validate-pbkdf2-settings-when-in-FIPS-mode.yaml + checksum: 5e60af2c83b5faf901fb5e504a1c042eb6cf97a2 + - kind: enhancement + summary: FIPS-capable agent file vault + description: | + Change elastic file vault implementation to allow variable length salt sizes + only in FIPS enabled agents. Increase default salt size to 16 for FIPS + compliance. Non-FIPS agents are unchanged. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7360 + issue: [] + timestamp: 1741808763 + file: + name: 1741808763-FIPS-Compliant-agent-file-vault.yaml + checksum: f20a224aeebd7585e36b202a452f74a485232286 + - kind: bug-fix + summary: Fix elasticsearch exporter configuration in kube-stack values + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1741865161 + file: + name: 1741865161-fix-otel-kube-stack-config.yaml + checksum: 469274d8e4bbe2cf8fd3eb02e6c5220ef1c1bdc8 + - kind: enhancement + summary: With this change FIPS-capable agents will only be able to upgrade to other FIPS-capable agents. This change also restricts non-fips to fips upgrades as well. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7312 + issue: + - https://github.com/elastic/ingest-dev/issues/4811 + timestamp: 1741897911 + file: + name: 1741897911-fips-to-fips-upgrades.yaml + checksum: a663c5dbda13750249ee3a61d4632103bbc63224 + - kind: enhancement + summary: Updated the error messages returned for fips upgrades + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7453 + issue: [] + timestamp: 1742318642 + file: + name: 1742318642-fips-to-fips-upgrade-error-reword.yaml + checksum: 21e493eaabcba3947fb371ec4983ac627f70c957 + - kind: enhancement + summary: Update OTel components to v0.121.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1743783374 + file: + name: 1743783374-update-otel-v0.121.0.yaml + checksum: 3491d3c13b6ebd1e7895b337d901d7df3e77dce1 + - kind: enhancement + summary: Update OTel components to v0.122.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7725 + issue: [] + timestamp: 1744022264 + file: + name: 1744022264-update-otel-components-to-v0.122.0.yaml + checksum: b22fa2630f29cd67191e62bec9b1f8a886c0e539 + - kind: bug-fix + summary: Correctly handle sending signal to child process + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7738 + issue: + - https://github.com/elastic/elastic-agent/issues/6875 + timestamp: 1744059162 + file: + name: 1744059162-send-correct-signal-on-windows.yaml + checksum: e6708089ece83e111bac8c85b20975ef5e877652 + - kind: feature + summary: Add nopexporter to EDOT Collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1744198660 + file: + name: 1744198660-add-nopexporter.yaml + checksum: 9f989be89459d35a8fdc48362a0dad19880fa4e1 + - kind: bug-fix + summary: Fix Managed OTLP Helm config to use current image repo. + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1744839123 + file: + name: 1744839123-fix-MOtel-config-image-value.yaml + checksum: cd9cb5f75e1b3983a48ee156e478e0a62051ffb6 + - kind: breaking-change + summary: '[otel] Disable process scraper of hostmetrics receiver' + description: | + The process scraper collects metrics for all available processes of a host without an easy way to limit + this to only report top N process for example. This results in quite big amount of timeseries. + Since this is not quite critical for any of the available UIs or dashboards we decide to disable + it temporarily until we find a better solution. Users that specifically need these metrics + can also enable it back manually. + Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/39423. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7894 + issue: [] + timestamp: 1744886313 + file: + name: 1744886313-otel_disable_process_scraper.yaml + checksum: 461df3d166c6ed60e8565e588b5ffce9078798ae + - kind: bug-fix + summary: | + Ship journalctl in the elastic-agent, elastic-agent-complete, and + elastic-otel-collector Docker images to enable reading journald + logs. Journalctl is not present on *-slim and all Wolfi images. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7995 + issue: + - https://github.com/elastic/beats/issues/44040 + timestamp: 1745609163 + file: + name: 1745609163-journalctl-on-all-docker-variants.yaml + checksum: a125369f2991dde7206d0e39ba90b37fb80ec9be + - kind: enhancement + summary: Update OTel components to v0.123.0 + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7996 + issue: [] + timestamp: 1745610677 + file: + name: 1745610677-update-otel-components-to-v0.123.0.yaml + checksum: b17b73a9fe45bfc44a92f0a8d64e2b8eca06dcd8 + - kind: bug-fix + summary: Preserve agent run state on DEB and RPM upgrades + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/7999 + issue: + - https://github.com/elastic/elastic-agent/issues/3832 + timestamp: 1745923884 + file: + name: 1745923884-deb-rpm-preserve-run-state.yaml + checksum: f4aa59929c389c20bc8104c8da4824979c3b8f35 + - kind: enhancement + summary: Retry enrollment requests on any error + description: | + If any error is encountered during an attempted enrollment, the elastic-agent + will backoff and retry. Add a new --enroll-timeout flag and + FLEET_ENROLL_TIMEOUT env var to set how long it tries for, default 10m. A + negative value disables the timeout. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8056 + issue: [] + timestamp: 1746113477 + file: + name: 1746113477-Retry-enrollment-for-all-errors.yaml + checksum: c5a6ee03401f35ef7737c67329850bff144de6cc + - kind: feature + summary: Adds a new configuration setting, `agent.upgrade.rollback.window` + description: | + The value of the `agent.upgrade.rollback.window` setting determines the period after upgrading + Elastic Agent when a rollback to the previous version can be triggered. This is an optional + setting, with a default value of `168h` (7 days). The value can be any string that is parseable + by https://pkg.go.dev/time#ParseDuration. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8065 + issue: + - https://github.com/elastic/elastic-agent/issues/6881 + timestamp: 1746197293 + file: + name: 1746197293-config-rollback-window.yaml + checksum: c8fad3780a06a39db30f98360292425143637db6 + - kind: bug-fix + summary: Use --header from enrollment when communicating with Fleet Server + description: | + The --header option for the enrollment command now adds the headers to the communication with Fleet Server. This + allows a proxy that requires specific headers present for traffic to flow to be placed in front of a Fleet Server + to be used and still allowing the Elastic Agent to enroll. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8071 + issue: + - https://github.com/elastic/elastic-agent/issues/6823 + timestamp: 1746213492 + file: + name: 1746213492-Add-header-to-enrollment-communication-with-Fleet-Server.yaml + checksum: d5cf474a8139caa874a432006dbdf5b7444d15b7 + - kind: other + summary: NOTICE.txt now contains only those modules that are used by the Elastic Agent binaries. + description: | + Only those modules that the Elastic Agent binaries for various platforms directly + or indirectly depend on are now included in the NOTICE.txt file . Modules used for development + tooling are now excluded from NOTICE.txt. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8053 + issue: [] + timestamp: 1746636264 + file: + name: 1746636264-fix-notice.yaml + checksum: 5e7c950a899c715c5c3bd7cc2c79e924f8f5585e + - kind: security + summary: Upgrade to Go 1.24.3. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8109 + issue: [] + timestamp: 1746652545 + file: + name: 1746652545-Upgrade-to-Go-1.24.3..yaml + checksum: c5b03e2e2685ef389a269f5904fdc53590c7e1b1 + - kind: other + summary: A new NOTICE file, `NOTICE-fips.txt` is included in FIPS-capable Agent distributions. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8124 + issue: [] + timestamp: 1746736812 + file: + name: 1746736812-fips-notice.yaml + checksum: 68827b357e51534ed8327d87bbb206f6606263c9 + - kind: bug-fix + summary: Address a race condition that can occur in Agent diagnostics if log rotation runs while logs are being zipped. + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1747938268 + file: + name: 1747938268-fix-diag-race-condition.yaml + checksum: 25e4883c6751a854d4a2f0897fb83848416c855e + - kind: enhancement + summary: Update OTel components to v0.125.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1749110938 + file: + name: 1749110938-update-otel-components-to-v0.125.0.yaml + checksum: 06e731438f75dd5a4f79952514ed9d22d556f101 + - kind: feature + summary: add cumulativetodeltaprocessor to EDOT collector + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1749176965 + file: + name: 1749176965-add-cumulativetodeltaprocessor.yaml + checksum: 6c4bc7565ed8fb801a1b02a01ee085488ae960e8 + - kind: bug-fix + summary: Use paths.TempDir for diagnostics actions + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8472 + issue: [] + timestamp: 1749742685 + file: + name: 1749742685-Use-paths.TempDir-for-diagnostics-actions.yaml + checksum: 1357d25b03d628ff7234a15a51e5dba89459d340 + - kind: feature + summary: Add apmconfig and apikeyauth OTel extensions + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1749824071 + file: + name: 1749824071-add-apmconfig-apikeyauth-extension.yaml + checksum: 2b92ba7906ac2c955bf32a47f46eb363c77ca323 + - kind: bug-fix + summary: Use Debian 11 to build linux/arm to match linux/amd64. Upgrades linux/arm64's statically linked glibc from 2.28 to 2.31. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8497 + issue: [] + timestamp: 1749844873 + file: + name: 1749844873-Use-Debian-11-for-linux-arm-to-match-linux-amd64.yaml + checksum: ddd1264b76219193cfed89ccc87e65b0144e4074 + - kind: bug-fix + summary: relax file ownership check to allow admin re-enrollment on Windows + description: | + On Windows, the agent previously enforced a strict file ownership (SID) check during re-enrollment, which prevented legitimate admin users from re-enrolling the agent if the owner did not match. This PR changes the Windows-specific logic to a no-op, allowing any admin to re-enroll the agent. This restores usability for admin users, but reintroduces the risk that privileged re-enrollment can break unprivileged installs. The Unix-specific ownership check remains unchanged. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8503 + issue: + - https://github.com/elastic/elastic-agent/issues/7794 + timestamp: 1749923633 + file: + name: 1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml + checksum: 650d0f58770863722ed75c0b092c4578f420e1fe + - kind: enhancement + summary: Update OTel components to v0.127.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1750008201 + file: + name: 1750008201-update-otel-components-to-v0.127.0.yaml + checksum: 0eacaaf0ba367d9597cf7b69bba487efef2bd31c + - kind: feature + summary: Add bearertokenauth Otel extension + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1750329445 + file: + name: 1750329445-add-bearertokenauth-extension.yaml + checksum: 321fc367b896aed8b01c802a75bd628ab149a608 + - kind: enhancement + summary: Remove deprecated otel elasticsearch exporter config `*_dynamic_index` from code and samples + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8592 + issue: [] + timestamp: 1750349806 + file: + name: 1750349806-elasticsearchexporter-deprecated-config.yaml + checksum: dc29806a5dc1e29c4842c1829d995ce4202e193f + - kind: feature + summary: Remove resource/k8s processor and use k8sattributes processor for service attributes + description: | + This PR removes the `resource/k8s` processor in honour of the k8sattributes processor that + provides native support for the Service attributes: + https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.127.0/processor/k8sattributesprocessor#configuring-recommended-resource-attributes + + This change is aligned with the respective Semantic Conventions' guidance: + https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#service-attributes + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8599 + issue: [] + timestamp: 1750408426 + file: + name: 1750408426-kube-stack-service-attrs.yaml + checksum: 4376b5e7140c31f3330fd7e7f69cf9bee8006bfb + - kind: upgrade + summary: Bump apmconfig extension to v0.3.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1750412496 + file: + name: 1750412496-bump-apmconfig-extension.yaml + checksum: 824f9b5a0bf1f70a6be92e916efbdcb6399fef86 + - kind: deprecation + summary: Deprecate the elasticinframetrics processor. It will be removed in 9.2.0. + description: "" + component: edot + pr: + - https://github.com/elastic/elastic-agent/pull/8659 + issue: [] + timestamp: 1750781638 + file: + name: 1750781638-Deprecate-the-elasticinframetrics-processor.yaml + checksum: 8c7df8e8a05808ac8279a65b3b32f6fd87f3fff9 + - kind: other + summary: Upgrade Synthetics NodeJS version to latest LTS v20. + description: "" + component: heartbeat + pr: + - https://github.com/elastic/elastic-agent/pull/8712 + issue: [] + timestamp: 1751029489 + file: + name: 1751029489-synth-upgra-node-v20.yaml + checksum: 26a735a19317db577652eea4bb1f3e863212da81 + - kind: bug-fix + summary: Remove incorrect logging that unprivileged installations are in beta. + description: 'Unprivileged installations went GA in 8.15.0: https://www.elastic.co/docs/reference/fleet/elastic-agent-unprivileged' + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8715 + issue: + - https://github.com/elastic/elastic-agent/issues/8689 + timestamp: 1751037802 + file: + name: 1751037802-Stop-logging-that-unprivileged-installations-are-in-beta.yaml + checksum: 2c2f731f90638eaf61e8ec021ce3c4dd8885ff3a + - kind: enhancement + summary: Include the forwardconnector as an EDOT collector commponent. + description: https://github.com/open-telemetry/opentelemetry-collector/tree/main/connector/forwardconnector + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8753 + issue: [] + timestamp: 1751317599 + file: + name: 1751317599-edot-collector-include-forwardconnector.yaml + checksum: 04412e4d8553807149ec868f1f5493441ea8e2cb + - kind: feature + summary: Add file logs only mOTEL kube-stack configuration + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751444462 + file: + name: 1751444462-add_logs_only_motel_config.yaml + checksum: a7768ce2ec6de109e7a9efae7793231f4965cf00 + - kind: bug-fix + summary: Ensure standalone Elastic Agent uses log level from configuration instead of persisted state + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8784 + issue: + - https://github.com/elastic/elastic-agent/issues/8137 + timestamp: 1751455886 + file: + name: 1751455886-correct-log-level-for-standalone-agents.yaml + checksum: e954db0ba6e1738e3d425cf3c8110a40c296a013 + - kind: enhancement + summary: Update OTel components to v0.129.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751458785 + file: + name: 1751458785-update-otel-components-to-v0.129.0.yaml + checksum: ee5c51c2d4a5cadd25bbf314358e09fb8cf906a5 + - kind: enhancement + summary: Update APM Config extension to v0.4.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751536568 + file: + name: 1751536568-update-apmconfig-extension-v0.4.0.yaml + checksum: 479c152af69e39e8651b7b7e6bbce51a804fc213 + - kind: enhancement + summary: Update Elastic Trace processor to v0.7.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751638649 + file: + name: 1751638649-update-elastictrace-processor-to-v0.7.0.yaml + checksum: 798e4080de8a1eefb2072f28db7402d2426e1f55 + - kind: enhancement + summary: Update Elastic APM connector to v0.4.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751638799 + file: + name: 1751638799-update-elasticapm-connector-to-v0.4.0.yaml + checksum: 2c17d9d7d90b1c3df280ffc5008dea62e5f075fe + - kind: enhancement + summary: Update API Key Auth extension to v0.2.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751639092 + file: + name: 1751639092-update-apikeyauth-extension-to-v0.2.0.yaml + checksum: 084a35923071e08433a2347aece8d1a6b028b214 + - kind: enhancement + summary: Update Elastic Infra Metrics processor to v0.16.0 + description: "" + component: elastic-agent + pr: [] + issue: [] + timestamp: 1751639206 + file: + name: 1751639206-update-elastic-infra-metrics-processor-to-v0.16.0.yaml + checksum: f14405b98aad0380ec5278bef6ae53c4e29ebd53 + - kind: bug-fix + summary: Resolve deadlocks in runtime checkin communication + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8881 + issue: + - https://github.com/elastic/elastic-agent/issues/7944 + timestamp: 1751960319 + file: + name: 1751960319-fix-blocking-issues-inside-runtime-communicator.yaml + checksum: d288cc7474997883bc2a9118b2abf150126c9d8c + - kind: bug-fix + summary: Removed init.d support from RPM packages + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/8896 + issue: + - https://github.com/elastic/elastic-agent/issues/8840 + timestamp: 1752049251 + file: + name: 1752049251-Fixed-SUSE-installation-from-RPM.yaml + checksum: bb9eba27e2dfa5885a2abd6140ea506d143b21f5 From 8d5d7e79381c59ae9d04e7c7f09d6542f76d970d Mon Sep 17 00:00:00 2001 From: Eric Beahan Date: Mon, 28 Jul 2025 15:58:24 -0500 Subject: [PATCH 3/4] cleanup --- changelog/9.1.0.asciidoc | 205 ++---------- changelog/9.1.0.yaml | 663 --------------------------------------- 2 files changed, 21 insertions(+), 847 deletions(-) diff --git a/changelog/9.1.0.asciidoc b/changelog/9.1.0.asciidoc index 987e3452102..49d7281e8f4 100644 --- a/changelog/9.1.0.asciidoc +++ b/changelog/9.1.0.asciidoc @@ -9,11 +9,9 @@ Review important information about the 9.1.0 release. [[security-updates-9.1.0]] === Security updates - elastic-agent:: -* Upgrade To Go 1.22.8. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5731[#https://github.com/elastic/elastic-agent/pull/5731] -* Upgrade To Go 1.24.3. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8109[#https://github.com/elastic/elastic-agent/pull/8109] +* Upgrade To Go 1.24.3. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8109[#https://github.com/elastic/elastic-agent/pull/8109] [discrete] [[breaking-changes-9.1.0]] @@ -27,61 +25,10 @@ impact to your application. elastic-agent:: -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/5481]] -.Remove Cloud-Defend From Agent Package. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5481[#https://github.com/elastic/elastic-agent/pull/5481] -[%collapsible] -==== - -==== -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/5536]] -.Remove Default Credentials When Running Elastic Agent In Container Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5536[#https://github.com/elastic/elastic-agent/pull/5536] -[%collapsible] -==== -ELASTICSEARCH_USERNAME and ELASTICSEARCH_PASSWORD now need to be explicitly set when running the agent in container mode -==== -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/5847]] -.Crossbuild-Debian11. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5847[#https://github.com/elastic/elastic-agent/pull/5847] -[%collapsible] -==== -We're dropping support for Debian 10, so no need to crossbuild using the outdated image anymore. This also updates the statically linked glibc from 2.19 to 2.31. -==== -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/6427]] -.Replace Default Ubuntu-Based Images With Ubi-Minimal-Based Ones. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6427[#https://github.com/elastic/elastic-agent/pull/6427] -[%collapsible] -==== - -==== -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/6461/files]] -.Removing --Path.install Option. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6461/files[#https://github.com/elastic/elastic-agent/pull/6461/files] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/2489[#https://github.com/elastic/elastic-agent/issues/2489] -[%collapsible] -==== - -==== -[discrete] -[[breaking-]] -.Changes To Binary Distribution. -[%collapsible] -==== -Default install installs only: - - agentbeat - - endpoint-security - - pf-host-agent -additional flag is added that includes components above and: - - cloudbeat - - apm-server - - fleet-server - - pf-elastic-symbolizer - - pf-elastic-collector - ==== [discrete] [[breaking-https://github.com/elastic/elastic-agent/pull/7894]] -.[Otel] Disable Process Scraper Of Hostmetrics Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7894[#https://github.com/elastic/elastic-agent/pull/7894] +.[Otel] Disable Process Scraper Of Hostmetrics Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7894[#https://github.com/elastic/elastic-agent/pull/7894] [%collapsible] ==== The process scraper collects metrics for all available processes of a host without an easy way to limit @@ -94,7 +41,6 @@ Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/iss ==== - [discrete] [[deprecations-9.1.0]] === Deprecations @@ -104,10 +50,9 @@ The following functionality is deprecated in 9.1.0, and will be removed in application, but we strongly recommend you make the necessary updates after you upgrade to 9.1.0. - edot:: -* Deprecate The Elasticinframetrics Processor. It Will Be Removed In 9.2.0. {edot-pull}https://github.com/elastic/elastic-agent/pull/8659[#https://github.com/elastic/elastic-agent/pull/8659] { $k | section}}::$k }}:: +* Deprecate The Elasticinframetrics Processor. It Will Be Removed In 9.2.0. {edot-pull}https://github.com/elastic/elastic-agent/pull/8659[#https://github.com/elastic/elastic-agent/pull/8659] [discrete] [[new-features-9.1.0]] @@ -115,61 +60,15 @@ edot:: The 9.1.0 release adds the following new and notable features. - - - -* Added Support For Pre-Existing Active Directory User For Unprivileged Mode. {-issue}https://github.com/elastic/elastic-agent/issues/4585[#https://github.com/elastic/elastic-agent/issues/4585] -+ -User can specify custom pre-existing user for running unprivileged mode. This user will be given permissions to log on as a service. -* Add Filesource Provider. {-pull}https://github.com/elastic/elastic-agent/pull/6587[#https://github.com/elastic/elastic-agent/pull/6587] {-issue}https://github.com/elastic/elastic-agent/issues/6362[#https://github.com/elastic/elastic-agent/issues/6362] -+ -filesource provider watches for changes of the files and updates the values of the variables -when the content of the file changes. - -* Add --Id And --Replace-Token To Enrollment. {-pull}https://github.com/elastic/elastic-agent/pull/6498[#https://github.com/elastic/elastic-agent/pull/6498] {-issue}https://github.com/elastic/elastic-agent/issues/6361[#https://github.com/elastic/elastic-agent/issues/6361] -+ -Add support for --id and --replace-token to the install and enroll command. Add support for ELASTIC_AGENT_ID -and FLEET_REPLACE_TOKEN to the container support the same behavior as the enroll command. Allows the ability to -define a specific ID to use for the Elastic Agent when enrolling into Fleet. The replace-token defines the token -that must be used to re-enroll an Elastic Agent with the same ID as a replacement of the previous Elastic Agent. - elastic-agent:: -* Upgrade-To-Go-1.24.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5309[#https://github.com/elastic/elastic-agent/pull/5309] -* Add Ability To Run Elastic Distribution Of Otel Collector At The Same Time As Other Inputs. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5767[#https://github.com/elastic/elastic-agent/pull/5767] -* Add Os_family, Os_platform And Os_version To Host Provider. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5941[#https://github.com/elastic/elastic-agent/pull/5941] {elastic-agent-issue}https://github.com/elastic/integrations/issues/10797[#https://github.com/elastic/integrations/issues/10797] -* Add Geoip Processor To Edot Collector. -* Add Metricbeat Otel Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6182[#https://github.com/elastic/elastic-agent/pull/6182] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6138[#https://github.com/elastic/elastic-agent/issues/6138] -* Add Opentelemetry Routing Connector To Edot Collector. -* Add Loadbalancing Exporter To Edot Collector. -* Removes `List` From Kibanafetchtoken In Favor Of `Items` As The Former Is Deprecated And Will Be Removed From The Api Response. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6437[#https://github.com/elastic/elastic-agent/pull/6437] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6023[#https://github.com/elastic/elastic-agent/issues/6023] -* Add Gateway Collector In Helm Kube-Stack Deployment. -* Add `Components` Command For `Otel` Mode. -* Add Receivercreator And K8sobserver To Edot Collector. -* Use A Random Free Port For Sub-Process Communication In Containers By Default. Avoids Port Collisions When Using Host Networking In Kubernetes. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6585[#https://github.com/elastic/elastic-agent/pull/6585] -* Add Kafkaexporter And Kafkareceiver To Edot Collector. {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6562[#https://github.com/elastic/elastic-agent/issues/6562] -* Add Jmxreceiver To Edot Collector. -* Add Nopreceiver To Edot Collector. -* Add Context Variable Support To Outputs. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6602[#https://github.com/elastic/elastic-agent/pull/6602] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6376[#https://github.com/elastic/elastic-agent/issues/6376] -+ -Adds support for using context variable providers in the outputs section of a policy. Includes fallback support -to reference env provider when no provider prefix is provided in the variable. - -* Add Nginx Receiver And Redis Receiver Otel Components. -* Add Motel Sample Configurations. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6630[#https://github.com/elastic/elastic-agent/pull/6630] -* Set Replicas For Gateway Collector. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7011[#https://github.com/elastic/elastic-agent/pull/7011] -* Add Nopexporter To Edot Collector. * Adds A New Configuration Setting, `Agent.upgrade.rollback.window`. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8065[#https://github.com/elastic/elastic-agent/pull/8065] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6881[#https://github.com/elastic/elastic-agent/issues/6881] + The value of the `agent.upgrade.rollback.window` setting determines the period after upgrading Elastic Agent when a rollback to the previous version can be triggered. This is an optional setting, with a default value of `168h` (7 days). The value can be any string that is parseable by https://pkg.go.dev/time#ParseDuration. - -* Add Cumulativetodeltaprocessor To Edot Collector. -* Add Apmconfig And Apikeyauth Otel Extensions. -* Add Bearertokenauth Otel Extension. -* Remove Resource/K8s Processor And Use K8sattributes Processor For Service Attributes. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8599[#https://github.com/elastic/elastic-agent/pull/8599] +* Remove Resource/K8s Processor And Use K8sattributes Processor For Service Attributes. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8599[#https://github.com/elastic/elastic-agent/pull/8599] + This PR removes the `resource/k8s` processor in honour of the k8sattributes processor that provides native support for the Service attributes: @@ -178,102 +77,40 @@ https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.127.0/ This change is aligned with the respective Semantic Conventions' guidance: https://opentelemetry.io/docs/specs/semconv/non-normative/k8s-attributes/#service-attributes -* Add File Logs Only Motel Kube-Stack Configuration. -elastic-agent,otel:: - -* Enable Persistence In The Configuration Provided With Our Otel Collector Distribution. {elastic-agent,otel-pull}https://github.com/elastic/elastic-agent/pull/5549[#https://github.com/elastic/elastic-agent/pull/5549] - - [discrete] [[enhancements-9.1.0]] === Enhancements - elastic-agent:: -* Support Elasticsearch_api_key Environment Variable When Running In Container Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5536[#https://github.com/elastic/elastic-agent/pull/5536] -* Add Filebeat Otel Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5833[#https://github.com/elastic/elastic-agent/pull/5833] -* Detect And Fail-Early Cli Upgrades If Agent Is Fleet-Managed. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/5864[#https://github.com/elastic/elastic-agent/pull/5864] -* Removed Endpoint Security From Linux Containers. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6016[#https://github.com/elastic/elastic-agent/pull/6016] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5495[#https://github.com/elastic/elastic-agent/issues/5495] -* Re-Enable Otel Subcommand On Windows. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6068[#https://github.com/elastic/elastic-agent/pull/6068] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/4976[#https://github.com/elastic/elastic-agent/issues/4976] -* Update Otel Components To V0.114.0. -* Elastic Agent Returns An Actionable Error Message When A The Use Trying To Execute The Enroll Command Is Not The Same As The Onwer Of The Elastic-Agent Program Files. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6144[#https://github.com/elastic/elastic-agent/pull/6144] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/4889[#https://github.com/elastic/elastic-agent/issues/4889] -* Only Run Providers Referenced In The Policy. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6169[#https://github.com/elastic/elastic-agent/pull/6169] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3609[#https://github.com/elastic/elastic-agent/issues/3609] -* Add A Flag To Skip Audit/Unenroll Call To Fleet Server During Uninstall. -* Update Otel Components To V0.115.0. -* Redact Common Secrets Like Api Keys And Passwords In The Output From `Inspect` Command. -* Prevent Leaking Secrets When Logging The Component Model. -* Embed Hints-Based Inputs In The Elastic Agent Container Image. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6381[#https://github.com/elastic/elastic-agent/pull/6381] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5661[#https://github.com/elastic/elastic-agent/issues/5661] -* Update Otel Components To V0.116.0. -* Windows Add Event Logging To Install, Uninstall, Enroll Failures. {elastic-agent-pull}https://github.com/elastic/elastic-agent/6410[#https://github.com/elastic/elastic-agent/6410] {elastic-agent-issue}https://github.com/elastic/elastic-agent/6338[#https://github.com/elastic/elastic-agent/6338] -* Added Logger To Print The Status And Code When Enrollment Call To Fleet Failed. {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6287[#https://github.com/elastic/elastic-agent/issues/6287] -* Update Otel Components To V0.117.0. -* Updated The Fleet Gateway So That When The Number Of Unauthorized Fleet Responses Exceeds The Set Limit, Instead Of Unenrolling, The Gateway Starts Checking In Less Frequently. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6619[#https://github.com/elastic/elastic-agent/pull/6619] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5428[#https://github.com/elastic/elastic-agent/issues/5428] -* Update Otel Components To V0.119.0. -* Improve Kubernetes_secrets Provider Secret Logging. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6841[#https://github.com/elastic/elastic-agent/pull/6841] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6187[#https://github.com/elastic/elastic-agent/issues/6187] -* Allow Upgrading Deb Or Rpm Agents When Using Elastic Defend With Tamper Protection. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6907[#https://github.com/elastic/elastic-agent/pull/6907] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6394[#https://github.com/elastic/elastic-agent/issues/6394] -* Add Apikey Prefix To Motel Host Configurations. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7063[#https://github.com/elastic/elastic-agent/pull/7063] * Add Elastic.agent.fips To Local_metadata. {elastic-agent-issue}https://github.com/elastic/elastic-agent/pull/7112[#https://github.com/elastic/elastic-agent/pull/7112] -* Validate Pbkdf2 Settings When In Fips Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7187[#https://github.com/elastic/elastic-agent/pull/7187] -* Fips-Capable Agent File Vault. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7360[#https://github.com/elastic/elastic-agent/pull/7360] +* Validate Pbkdf2 Settings When In Fips Mode. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7187[#https://github.com/elastic/elastic-agent/pull/7187] +* Fips-Capable Agent File Vault. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7360[#https://github.com/elastic/elastic-agent/pull/7360] * With This Change Fips-Capable Agents Will Only Be Able To Upgrade To Other Fips-Capable Agents. This Change Also Restricts Non-Fips To Fips Upgrades As Well. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7312[#https://github.com/elastic/elastic-agent/pull/7312] {elastic-agent-issue}https://github.com/elastic/ingest-dev/issues/4811[#https://github.com/elastic/ingest-dev/issues/4811] -* Updated The Error Messages Returned For Fips Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7453[#https://github.com/elastic/elastic-agent/pull/7453] -* Update Otel Components To V0.121.0. -* Update Otel Components To V0.122.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7725[#https://github.com/elastic/elastic-agent/pull/7725] -* Update Otel Components To V0.123.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7996[#https://github.com/elastic/elastic-agent/pull/7996] -* Retry Enrollment Requests On Any Error. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8056[#https://github.com/elastic/elastic-agent/pull/8056] -* Update Otel Components To V0.125.0. -* Update Otel Components To V0.127.0. -* Remove Deprecated Otel Elasticsearch Exporter Config `*_Dynamic_index` From Code And Samples. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8592[#https://github.com/elastic/elastic-agent/pull/8592] -* Include The Forwardconnector As An Edot Collector Commponent. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8753[#https://github.com/elastic/elastic-agent/pull/8753] -* Update Otel Components To V0.129.0. -* Update Apm Config Extension To V0.4.0. -* Update Elastic Trace Processor To V0.7.0. -* Update Elastic Apm Connector To V0.4.0. -* Update Api Key Auth Extension To V0.2.0. -* Update Elastic Infra Metrics Processor To V0.16.0. - - -[discrete] -[[upgrades-9.1.0]] -=== Upgrades - - -elastic-agent:: - -* Bump Apmconfig Extension To V0.3.0. - +* Updated The Error Messages Returned For Fips Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7453[#https://github.com/elastic/elastic-agent/pull/7453] +* Retry Enrollment Requests On Any Error. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8056[#https://github.com/elastic/elastic-agent/pull/8056] +* Remove Deprecated Otel Elasticsearch Exporter Config `*_Dynamic_index` From Code And Samples. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8592[#https://github.com/elastic/elastic-agent/pull/8592] +* Include The Forwardconnector As An Edot Collector Commponent. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8753[#https://github.com/elastic/elastic-agent/pull/8753] +* Update Otel Components To V0.129.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Update Apm Config Extension To V0.4.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Update Elastic Trace Processor To V0.7.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Update Elastic Apm Connector To V0.4.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Update Api Key Auth Extension To V0.2.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Update Elastic Infra Metrics Processor To V0.16.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] +* Bump Apmconfig Extension To V0.3.0. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8819[#https://github.com/elastic/elastic-agent/pull/8819] [discrete] [[bug-fixes-9.1.0]] === Bug fixes - - - -* Notify Fleet Of Uninstall On Windows. {-pull}https://github.com/elastic/elastic-agent/pull/6257[#https://github.com/elastic/elastic-agent/pull/6257] {-issue}https://github.com/elastic/elastic-agent/issues/5952[#https://github.com/elastic/elastic-agent/issues/5952] -* Fix Deadlock In Otelmanager. {-pull}https://github.com/elastic/elastic-agent/pull/6927[#https://github.com/elastic/elastic-agent/pull/6927] elastic-agent:: -* Prevent Installing Elastic Defend On Non Native Architecture. -* Added Retries For Requesting Download Verifiers When Upgrading The Agent. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6276[#https://github.com/elastic/elastic-agent/pull/6276] -* The Install Command Is Updated So That If A User Installs An Agent, While There Is Already An Agent, Using The `--Force` Flag Replaces The Correct One. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6559[#https://github.com/elastic/elastic-agent/pull/6559] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/5595[#https://github.com/elastic/elastic-agent/issues/5595] -* Fix Enrollment For Containerised Agent When Enrollment Token Changes Or The Agent Is Unenrolled. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6568[#https://github.com/elastic/elastic-agent/pull/6568] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3586[#https://github.com/elastic/elastic-agent/issues/3586] -* Fix Logical Race Conditions In Kubernetes_secrets Provider. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/6623[#https://github.com/elastic/elastic-agent/pull/6623] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6340[#https://github.com/elastic/elastic-agent/issues/6340] -* Fix Tsdb Version_conflict_engine_exception Caused By Incorrect Kube-Stack Helm Values. -* Support Ipv6 Host In Agent Monitoring Http Config. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7073[#https://github.com/elastic/elastic-agent/pull/7073] -* Fix Elasticsearch Exporter Configuration In Kube-Stack Values. * Correctly Handle Sending Signal To Child Process. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7738[#https://github.com/elastic/elastic-agent/pull/7738] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6875[#https://github.com/elastic/elastic-agent/issues/6875] -* Fix Managed Otlp Helm Config To Use Current Image Repo. -* Ship Journalctl In The Elastic-Agent, Elastic-Agent-Complete, And -Elastic-Otel-Collector Docker Images To Enable Reading Journald -Logs. Journalctl Is Not Present On *-Slim And All Wolfi Images. -. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7995[#https://github.com/elastic/elastic-agent/pull/7995] {elastic-agent-issue}https://github.com/elastic/beats/issues/44040[#https://github.com/elastic/beats/issues/44040] -* Preserve Agent Run State On Deb And Rpm Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7999[#https://github.com/elastic/elastic-agent/pull/7999] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/3832[#https://github.com/elastic/elastic-agent/issues/3832] +* Preserve Agent Run State On Deb And Rpm Upgrades. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7999[#https://github.com/elastic/elastic-agent/pull/7999] * Use --Header From Enrollment When Communicating With Fleet Server. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8071[#https://github.com/elastic/elastic-agent/pull/8071] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/6823[#https://github.com/elastic/elastic-agent/issues/6823] -* Address A Race Condition That Can Occur In Agent Diagnostics If Log Rotation Runs While Logs Are Being Zipped. -* Use Paths.tempdir For Diagnostics Actions. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8472[#https://github.com/elastic/elastic-agent/pull/8472] -* Use Debian 11 To Build Linux/Arm To Match Linux/Amd64. Upgrades Linux/Arm64's Statically Linked Glibc From 2.28 To 2.31. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8497[#https://github.com/elastic/elastic-agent/pull/8497] +* Address A Race Condition That Can Occur In Agent Diagnostics If Log Rotation Runs While Logs Are Being Zipped. +* Use Paths.tempdir For Diagnostics Actions. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8472[#https://github.com/elastic/elastic-agent/pull/8472] +* Use Debian 11 To Build Linux/Arm To Match Linux/Amd64. Upgrades Linux/Arm64's Statically Linked Glibc From 2.28 To 2.31. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8497[#https://github.com/elastic/elastic-agent/pull/8497] * Relax File Ownership Check To Allow Admin Re-Enrollment On Windows. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8503[#https://github.com/elastic/elastic-agent/pull/8503] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/7794[#https://github.com/elastic/elastic-agent/issues/7794] * Remove Incorrect Logging That Unprivileged Installations Are In Beta. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8715[#https://github.com/elastic/elastic-agent/pull/8715] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8689[#https://github.com/elastic/elastic-agent/issues/8689] * Ensure Standalone Elastic Agent Uses Log Level From Configuration Instead Of Persisted State. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8784[#https://github.com/elastic/elastic-agent/pull/8784] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/8137[#https://github.com/elastic/elastic-agent/issues/8137] diff --git a/changelog/9.1.0.yaml b/changelog/9.1.0.yaml index 4b7f5b9f704..059512993be 100644 --- a/changelog/9.1.0.yaml +++ b/changelog/9.1.0.yaml @@ -1,605 +1,5 @@ version: 9.1.0 entries: - - kind: feature - summary: Upgrade-to-Go-1.24.0 - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5309 - issue: [] - timestamp: 1723829102 - file: - name: 1723829102-Upgrade-to-Go-1.23.0.yaml - checksum: 85618dbc474cb2a75c33ad9eb31600a3b07b230a - - kind: breaking-change - summary: Remove cloud-defend from agent package - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5481 - issue: [] - timestamp: 1725913991 - file: - name: 1725913991-remove-cloud-defend.yaml - checksum: 5bc3b5e31f850ce19da3ff2bdd0f6710a15efb06 - - kind: breaking-change - summary: Remove default credentials when running Elastic Agent in container mode - description: ELASTICSEARCH_USERNAME and ELASTICSEARCH_PASSWORD now need to be explicitly set when running the agent in container mode - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5536 - issue: [] - timestamp: 1726144746 - file: - name: 1726144746-container-default-credentials.yaml - checksum: 787ea64973b0a62effa8d92fc308bf95ad084d9d - - kind: enhancement - summary: Support ELASTICSEARCH_API_KEY environment variable when running in container mode - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5536 - issue: [] - timestamp: 1726145045 - file: - name: 1726145045-container-api-key.yaml - checksum: 80738c5524291194c91c457bdfb5baf80a339522 - - kind: feature - summary: Enable persistence in the configuration provided with our OTel Collector distribution. - description: "" - component: elastic-agent,otel - pr: - - https://github.com/elastic/elastic-agent/pull/5549 - issue: [] - timestamp: 1726572104 - file: - name: 1726572104-enable-persistence-by-default.yaml - checksum: 9f79bc53034a5d6e7c00f14dbb90682bb2331328 - - kind: security - summary: Upgrade to Go 1.22.8. - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5731 - issue: [] - timestamp: 1728332120 - file: - name: 1728332120-Upgrade-to-Go-1.22.8..yaml - checksum: 959431da51ad449f61effe2d131c8ab87139e731 - - kind: feature - summary: Add ability to run Elastic Distribution of OTel Collector at the same time as other inputs - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5767 - issue: [] - timestamp: 1729011748 - file: - name: 1729011748-Add-EDOT-hybrid-mode.yaml - checksum: 83f6f4cb37cb776770ca9ff99b39228b9529df54 - - kind: enhancement - summary: Add filebeat otel receiver - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5833 - issue: [] - timestamp: 1729630977 - file: - name: 1729630977-Add-filebeat-otel-receiver.yaml - checksum: 0e5e55864891cc5896a90a015decd87e8f463556 - - kind: breaking-change - summary: crossbuild-debian11 - description: We're dropping support for Debian 10, so no need to crossbuild using the outdated image anymore. This also updates the statically linked glibc from 2.19 to 2.31. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5847 - issue: [] - timestamp: 1729750939 - file: - name: 1729750939-crossbuild-debian11.yaml - checksum: 4972f2ef7a2315f39713345eb471a00a0573eff8 - - kind: enhancement - summary: Detect and fail-early cli upgrades if agent is fleet-managed - description: This change brings restrictions on the upgrade cli command. If an agent is fleet-managed and is running in unprivileged mode, users won't be able to upgrade the agent using the cli. If an agent is fleet-managed and is running privileged, users will only be able to upgrade the agent using the cli if they provide --force flag. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5864 - issue: [] - timestamp: 1729971565 - file: - name: 1729971565-detect-fail-early-fleet-managed-cli-upgrade.yaml - checksum: 9e787dd2741fe58524f9736d969f35a0b1dcbecb - - kind: feature - summary: Add os_family, os_platform and os_version to host provider - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/5941 - issue: - - https://github.com/elastic/integrations/issues/10797 - timestamp: 1730986549 - file: - name: 1730986549-Add-os_family,-os_platform-and-os_version-to-host-provider.yaml - checksum: f2dabf4cc393c6a4bd1c6e30d8fdd6f8ba71fc19 - - kind: feature - summary: Added support for pre-existing Active Directory user for unprivileged mode - description: User can specify custom pre-existing user for running unprivileged mode. This user will be given permissions to log on as a service. - component: "" - pr: [] - issue: - - https://github.com/elastic/elastic-agent/issues/4585 - timestamp: 1731314919 - file: - name: 1731314919-Added-support-for-custom-Active-Directory-user-for-unprivileged-mode.yaml - checksum: 1bba4dcbe7d1a12549a958c7849900a3018102c1 - - kind: enhancement - summary: removed endpoint security from linux containers - description: Removed elastic endpoint security from linux containers as it has a dependency on systemd. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6016 - issue: - - https://github.com/elastic/elastic-agent/issues/5495 - timestamp: 1731517501 - file: - name: 1731517501-removed-endpoint-security-from-linux-containers.yaml - checksum: 73ce73dcbe55f9a094386af3ce0db5d13327d63e - - kind: enhancement - summary: re-enable otel subcommand on Windows - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6068 - issue: - - https://github.com/elastic/elastic-agent/issues/4976 - timestamp: 1731962301 - file: - name: 1731962301-re-enable-otel-subcommand-on-Windows.yaml - checksum: ea1fe69816ff322cb2cc91ccf32812a4cb5b503c - - kind: bug-fix - summary: Prevent installing Elastic Defend on non native architecture - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1732110636 - file: - name: 1732110636-elastic-defend-cannot-run-in-emulation.yaml - checksum: cc811ca8793718da37ee77b8dfdcc38bf28ed8eb - - kind: enhancement - summary: Update OTel components to v0.114.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1732187698 - file: - name: 1732187698-update-otel-v0.114.0.yaml - checksum: 34dc5f9c30bbfd353a2fb037ec36eb36afefb9c6 - - kind: enhancement - summary: Elastic agent returns an actionable error message when a the use trying to execute the enroll command is not the same as the onwer of the elastic-agent program files - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6144 - issue: - - https://github.com/elastic/elastic-agent/issues/4889 - timestamp: 1732656422 - file: - name: 1732656422-add-actionable-error-message-for-enroll-command.yaml - checksum: 26a631d17865361a1dd4c8fee8b14c27e7141ef7 - - kind: feature - summary: add GeoIP processor to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1732809895 - file: - name: 1732809895-add-GeoIP-processor-to-EDOT-collector.yaml - checksum: 277f35b0578e38c852c8b70106d2be39d6bec337 - - kind: enhancement - summary: Only run providers referenced in the policy - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6169 - issue: - - https://github.com/elastic/elastic-agent/issues/3609 - timestamp: 1732840106 - file: - name: 1732840106-Only-run-providers-referenced-in-the-policy.yaml - checksum: 0cc32a70c3ce3907a4a97032e870d5ab2f558b3c - - kind: feature - summary: add metricbeat otel receiver - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6182 - issue: - - https://github.com/elastic/elastic-agent/issues/6138 - timestamp: 1733156311 - file: - name: 1733156311-add-metricbeat-otel-receiver.yaml - checksum: b288610f75f9885b18152142766d7f3ef7da32b6 - - kind: enhancement - summary: Add a flag to skip audit/unenroll call to fleet server during uninstall - description: This change adds a flag to skip audit/unenroll call to fleet server. While uninstalling elastic-agent it tries to notify fleet server about the uninstallation. But in somecases users might know that the fleet server is unreachable and this notification logs multiple failures continuously. Adding this flag skips this call. - component: elastic-agent - pr: [] - issue: [] - timestamp: 1733248787 - file: - name: 1733248787-flag-to-skip-fleet-audit.yaml - checksum: 90feaadcd5767184283b24e3d939e733974d8dc4 - - kind: feature - summary: Add OpenTelemetry Routing connector to EDOT Collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1733317274 - file: - name: 1733317274-add-routing-connector-to-EDOT-collector.yaml - checksum: 97ad4a46f22735875d557534e2c11d4874e3ced4 - - kind: enhancement - summary: Update OTel components to v0.115.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1733390040 - file: - name: 1733390040-update-otel-0.115.0.yaml - checksum: a5e553950b636961aa866fabd996cc98cf4d674f - - kind: enhancement - summary: Redact common secrets like API keys and passwords in the output from `inspect` command - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1733397457 - file: - name: 1733397457-redact-common-secrets-in-inspect-output.yaml - checksum: 3a6f322345d0be9b1b7babcd283360461097d9f4 - - kind: bug-fix - summary: Notify Fleet of uninstall on Windows - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/6257 - issue: - - https://github.com/elastic/elastic-agent/issues/5952 - timestamp: 1733768621 - file: - name: 1733768621-Notify-Fleet-of-uninstall-on-Windows.yaml - checksum: 2261f729d790b28259c486904351e809fe15ddd3 - - kind: bug-fix - summary: added retries for requesting download verifiers when upgrading the agent - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6276 - issue: [] - timestamp: 1733936340 - file: - name: 1733936340-add-retries-for-download-upgrade-verifiers.yaml - checksum: 4ff5442cc287002e52df7244387e7ef464ee2ffc - - kind: feature - summary: add loadbalancing exporter to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1734023789 - file: - name: 1734023789-add-loadbalancing-exporter-to-EDOT-collector.yaml - checksum: f94fb4193a2f051b82ff70ce5ffa738df36cdb17 - - kind: enhancement - summary: Prevent leaking secrets when logging the component model - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1734098868 - file: - name: 1734098868-prevent-leaking-secrets-when-logging-component-model.yaml - checksum: f97e506ed1e434803b4f98914526b461d013f414 - - kind: enhancement - summary: Embed hints-based inputs in the Elastic Agent container image. - description: This change includes the addition of hints-based inputs directly within the Elastic Agent container image, enabling streamlined configurations for input discovery when deployed in containerized environments. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6381 - issue: - - https://github.com/elastic/elastic-agent/issues/5661 - timestamp: 1734512365 - file: - name: 1734512365-embed-hints-inputs-in-agent-container-image.yaml - checksum: 377396eb3d0baf5ee407947ab72eedfe50ff5c37 - - kind: enhancement - summary: Update OTel components to v0.116.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1734525166 - file: - name: 1734525166-update-otel-v0.116.0.yaml - checksum: 60cb22ef685dfcbf9ef1a97d6d64e40d5eca45c3 - - kind: enhancement - summary: Windows add Event Logging to install, uninstall, enroll failures - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/6410 - issue: - - https://github.com/elastic/elastic-agent/6338 - timestamp: 1734626964 - file: - name: 1734626964-Windows-add-Event-Logging-to-install,-uninstall,-enroll.yaml - checksum: e9bafab97ec550ab78494e4f10f5784cc1d80a39 - - kind: breaking-change - summary: Replace default Ubuntu-based images with UBI-minimal-based ones - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6427 - issue: [] - timestamp: 1734959878 - file: - name: 1734959878-Replace-default-Ubuntu-based-images-with-UBI-minimal-based-ones.yaml - checksum: b8ab6a7dbab04b70007a37fb11224f10c4c7e943 - - kind: feature - summary: removes `list` from kibanaFetchToken in favor of `items` as the former is deprecated and will be removed from the api response - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6437 - issue: - - https://github.com/elastic/elastic-agent/issues/6023 - timestamp: 1735137195 - file: - name: 1735137195-remove-deprecated-list-in-favor-of-items.yaml - checksum: 23a9ecf8dad6f29e58581a41e9b8b5ee348c5cba - - kind: feature - summary: add gateway collector in Helm kube-stack deployment - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1735306293 - file: - name: 1735306293-add-gateway-collector-in-Helm-kube-stack-deployment.yaml - checksum: 6ca30d0b19e24fa27872fcd292d10fc31abbb30a - - kind: breaking-change - summary: Removing --path.install option - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6461/files - issue: - - https://github.com/elastic/elastic-agent/issues/2489 - timestamp: 1735664420 - file: - name: 1735664420-remove-deprecated-path-install-cli-flag.yaml - checksum: ceedae40882bfee7db7f8eb0c0b1e8fdd4290638 - - kind: enhancement - summary: Added logger to print the status and code when enrollment call to fleet failed. - description: "" - component: elastic-agent - pr: [] - issue: - - https://github.com/elastic/elastic-agent/issues/6287 - timestamp: 1736002257 - file: - name: 1736002257-log-fleet-enroll-failure-status-code.yaml - checksum: 725fe14f2e5e6a361b8ce21c44ecb37c25c6b4ac - - kind: enhancement - summary: Update OTel components to v0.117.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1736417404 - file: - name: 1736417404-update-otel-v0.117.0.yaml - checksum: 391d8bb42bc60ded03da5d51c579e67baf29ae91 - - kind: feature - summary: Add `components` command for `otel` mode. - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1737106864 - file: - name: 1737106864-add_otel_components_cmd.yaml - checksum: ed1b96a2a42183ce554618f93d199a28a33407d4 - - kind: breaking-change - summary: Changes to binary distribution - description: | - Default install installs only: - - agentbeat - - endpoint-security - - pf-host-agent - additional flag is added that includes components above and: - - cloudbeat - - apm-server - - fleet-server - - pf-elastic-symbolizer - - pf-elastic-collector - component: elastic-agent - pr: [] - issue: [] - timestamp: 1737131552 - file: - name: 1737131552-Changes-to-binary-distribution.yaml - checksum: 2e5094fc0897c99c63089c7a64294197a2772633 - - kind: feature - summary: Add receivercreator and k8sobserver to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1737462864 - file: - name: 1737462864-add_k8s_otel_comps.yaml - checksum: 965a483f6d19b83f62b49e0b29dc00f7720baf20 - - kind: bug-fix - summary: The install command is updated so that if a user installs an agent, while there is already an agent, using the `--force` flag replaces the correct one. - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6559 - issue: - - https://github.com/elastic/elastic-agent/issues/5595 - timestamp: 1737473147 - file: - name: 1737473147-force-install-replaces-correct-agent.yaml - checksum: b859983d69d2c1bf215fa0b3448cb49ee695e866 - - kind: bug-fix - summary: Fix enrollment for containerised agent when enrollment token changes or the agent is unenrolled - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6568 - issue: - - https://github.com/elastic/elastic-agent/issues/3586 - timestamp: 1737552345 - file: - name: 1737552345-Fix-enrollment-for-containerised-agent-when-there-is-an-enrollement-token-change-or-the-agent-is-unenrolled.yaml - checksum: 271f8551f709ec1e7be7e175c792a48a897cf6cc - - kind: feature - summary: Use a random free port for sub-process communication in containers by default. Avoids port collisions when using host networking in Kubernetes. - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6585 - issue: [] - timestamp: 1737657890 - file: - name: 1737657890-Use-a-random-free-port-for-sub-process-communication-in-containers.yaml - checksum: d8fe375db50cd5643eb921a0e4ec4e541040b95b - - kind: feature - summary: Add filesource provider - description: | - filesource provider watches for changes of the files and updates the values of the variables - when the content of the file changes. - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/6587 - issue: - - https://github.com/elastic/elastic-agent/issues/6362 - timestamp: 1737666699 - file: - name: 1737666699-Add-filesource-provider.yaml - checksum: 7f858f76eadbfb558d861f03bc49c088b46e02e1 - - kind: feature - summary: add kafkaexporter and kafkareceiver to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: - - https://github.com/elastic/elastic-agent/issues/6562 - timestamp: 1737717648 - file: - name: 1737717648-add-kafkaexporter-otel-collector.yaml - checksum: 62a4f53c8d07652832ca7ffb7fb0abac8a9b9c19 - - kind: feature - summary: add jmxreceiver to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1737749181 - file: - name: 1737749181-add-jmxreceiver-otel-collector.yaml - checksum: b5ba5a564aa217b8c827b74cc19941690de56312 - - kind: feature - summary: add nopreceiver to EDOT collector - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1737750331 - file: - name: 1737750331-add-nopreceiver-otel-collector.yaml - checksum: 5658543bbbb08bf6b4b46e5cebe51f51c1f998aa - - kind: feature - summary: Add context variable support to outputs - description: | - Adds support for using context variable providers in the outputs section of a policy. Includes fallback support - to reference env provider when no provider prefix is provided in the variable. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6602 - issue: - - https://github.com/elastic/elastic-agent/issues/6376 - timestamp: 1737816507 - file: - name: 1737816507-Add-context-variable-support-to-outputs.yaml - checksum: a48fcb465af0ff61da95e7833f324f297457c3a2 - - kind: bug-fix - summary: Fix logical race conditions in kubernetes_secrets provider - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6623 - issue: - - https://github.com/elastic/elastic-agent/issues/6340 - timestamp: 1738139927 - file: - name: 1738139927-Fix-logical-race-conditions-in-kubernetes_secrets-provider.yaml - checksum: 4ab7092ac0cdc741dfb2d9eb8e309bcf9e10916a - - kind: feature - summary: Add Nginx receiver and Redis receiver OTel components - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1738160406 - file: - name: 1738160406-add_redis_nginx_otel_comps.yaml - checksum: f15594711ea1346dd4e5322addec37903ce18bc2 - - kind: enhancement - summary: Updated the fleet gateway so that when the number of unauthorized fleet responses exceeds the set limit, instead of unenrolling, the gateway starts checking in less frequently. - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6619 - issue: - - https://github.com/elastic/elastic-agent/issues/5428 - timestamp: 1738199968 - file: - name: 1738199968-update-scheduler-when-received-too-many-unathorized-responses.yaml - checksum: f3c25d66824668cdb1a227fa4e4fd49decfa51a2 - - kind: enhancement - summary: Update OTel components to v0.119.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1738752554 - file: - name: 1738752554-update-otel-v0.119.0.yaml - checksum: acf16fd9e6005926f4949b78717daae9648b837e - - kind: feature - summary: Add --id and --replace-token to enrollment - description: | - Add support for --id and --replace-token to the install and enroll command. Add support for ELASTIC_AGENT_ID - and FLEET_REPLACE_TOKEN to the container support the same behavior as the enroll command. Allows the ability to - define a specific ID to use for the Elastic Agent when enrolling into Fleet. The replace-token defines the token - that must be used to re-enroll an Elastic Agent with the same ID as a replacement of the previous Elastic Agent. - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/6498 - issue: - - https://github.com/elastic/elastic-agent/issues/6361 - timestamp: 1738784301 - file: - name: 1738784301-Add-id-and-replace-token-to-enrollment.yaml - checksum: db7f63d59e142273afd4a884e2cf7a60a9661187 - kind: enhancement summary: Improve kubernetes_secrets provider secret logging description: "" @@ -612,17 +12,6 @@ entries: file: name: 1739437836-Improve-kubernetes_secrets-provider-secret-logging.yaml checksum: 0c4b850fae555d18f7a8ba5292f668a28483eaf2 - - kind: feature - summary: add MOtel sample configurations - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/6630 - issue: [] - timestamp: 1739544282 - file: - name: 1739544282-add-MOtel-sample-configurations.yaml - checksum: 06334af7feea3aec65ceed7678a960567525869c - kind: bug-fix summary: Fix deadlock in OTelManager description: | @@ -762,27 +151,6 @@ entries: file: name: 1742318642-fips-to-fips-upgrade-error-reword.yaml checksum: 21e493eaabcba3947fb371ec4983ac627f70c957 - - kind: enhancement - summary: Update OTel components to v0.121.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1743783374 - file: - name: 1743783374-update-otel-v0.121.0.yaml - checksum: 3491d3c13b6ebd1e7895b337d901d7df3e77dce1 - - kind: enhancement - summary: Update OTel components to v0.122.0 - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/7725 - issue: [] - timestamp: 1744022264 - file: - name: 1744022264-update-otel-components-to-v0.122.0.yaml - checksum: b22fa2630f29cd67191e62bec9b1f8a886c0e539 - kind: bug-fix summary: Correctly handle sending signal to child process description: "" @@ -847,17 +215,6 @@ entries: file: name: 1745609163-journalctl-on-all-docker-variants.yaml checksum: a125369f2991dde7206d0e39ba90b37fb80ec9be - - kind: enhancement - summary: Update OTel components to v0.123.0 - description: "" - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/7996 - issue: [] - timestamp: 1745610677 - file: - name: 1745610677-update-otel-components-to-v0.123.0.yaml - checksum: b17b73a9fe45bfc44a92f0a8d64e2b8eca06dcd8 - kind: bug-fix summary: Preserve agent run state on DEB and RPM upgrades description: "" @@ -962,16 +319,6 @@ entries: file: name: 1747938268-fix-diag-race-condition.yaml checksum: 25e4883c6751a854d4a2f0897fb83848416c855e - - kind: enhancement - summary: Update OTel components to v0.125.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1749110938 - file: - name: 1749110938-update-otel-components-to-v0.125.0.yaml - checksum: 06e731438f75dd5a4f79952514ed9d22d556f101 - kind: feature summary: add cumulativetodeltaprocessor to EDOT collector description: "" @@ -1027,16 +374,6 @@ entries: file: name: 1749923633-Windows-relax-file-ownership-check-for-re-enrollment.yaml checksum: 650d0f58770863722ed75c0b092c4578f420e1fe - - kind: enhancement - summary: Update OTel components to v0.127.0 - description: "" - component: elastic-agent - pr: [] - issue: [] - timestamp: 1750008201 - file: - name: 1750008201-update-otel-components-to-v0.127.0.yaml - checksum: 0eacaaf0ba367d9597cf7b69bba487efef2bd31c - kind: feature summary: Add bearertokenauth Otel extension description: "" From 771ddd23727607dbc8b872532185cbfd730f3188 Mon Sep 17 00:00:00 2001 From: Eric Beahan Date: Fri, 1 Aug 2025 17:12:51 -0500 Subject: [PATCH 4/4] remove entry added in 9.0.1 changelog --- changelog/9.1.0.asciidoc | 28 ---------------------------- changelog/9.1.0.yaml | 17 ----------------- 2 files changed, 45 deletions(-) diff --git a/changelog/9.1.0.asciidoc b/changelog/9.1.0.asciidoc index 49d7281e8f4..f33831cf4a4 100644 --- a/changelog/9.1.0.asciidoc +++ b/changelog/9.1.0.asciidoc @@ -13,34 +13,6 @@ elastic-agent:: * Upgrade To Go 1.24.3. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/8109[#https://github.com/elastic/elastic-agent/pull/8109] -[discrete] -[[breaking-changes-9.1.0]] -=== 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. - -// TODO: add details and impact - -elastic-agent:: - -==== -[discrete] -[[breaking-https://github.com/elastic/elastic-agent/pull/7894]] -.[Otel] Disable Process Scraper Of Hostmetrics Receiver. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/7894[#https://github.com/elastic/elastic-agent/pull/7894] -[%collapsible] -==== -The process scraper collects metrics for all available processes of a host without an easy way to limit -this to only report top N process for example. This results in quite big amount of timeseries. -Since this is not quite critical for any of the available UIs or dashboards we decide to disable -it temporarily until we find a better solution. Users that specifically need these metrics -can also enable it back manually. -Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/39423. - -==== - - [discrete] [[deprecations-9.1.0]] === Deprecations diff --git a/changelog/9.1.0.yaml b/changelog/9.1.0.yaml index 059512993be..70ea8c7749d 100644 --- a/changelog/9.1.0.yaml +++ b/changelog/9.1.0.yaml @@ -183,23 +183,6 @@ entries: file: name: 1744839123-fix-MOtel-config-image-value.yaml checksum: cd9cb5f75e1b3983a48ee156e478e0a62051ffb6 - - kind: breaking-change - summary: '[otel] Disable process scraper of hostmetrics receiver' - description: | - The process scraper collects metrics for all available processes of a host without an easy way to limit - this to only report top N process for example. This results in quite big amount of timeseries. - Since this is not quite critical for any of the available UIs or dashboards we decide to disable - it temporarily until we find a better solution. Users that specifically need these metrics - can also enable it back manually. - Related to https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/39423. - component: elastic-agent - pr: - - https://github.com/elastic/elastic-agent/pull/7894 - issue: [] - timestamp: 1744886313 - file: - name: 1744886313-otel_disable_process_scraper.yaml - checksum: 461df3d166c6ed60e8565e588b5ffce9078798ae - kind: bug-fix summary: | Ship journalctl in the elastic-agent, elastic-agent-complete, and