From 03ef9d8d6a894af61a77d78983a735d263b414ac Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Wed, 8 Nov 2023 14:12:18 +0100 Subject: [PATCH] Changelog for 8.11.0 (#3722) * Changelog for 8.11.0 * Remove an entry in the changelog --- changelog/8.11.0.asciidoc | 107 ++++++++++ changelog/8.11.0.yaml | 182 ++++++++++++++++++ ...cessor-support-for-hints-autodiscover.yaml | 32 --- .../1693427183-install-progress.yaml | 32 --- .../1693813219-log-command-colors.yaml | 31 --- .../1693920861-netinfo-manifests.yaml | 32 --- ...and-kills-any-running-watcher-process.yaml | 32 --- .../1694439479-fix_creatork8sscript.yaml | 32 --- ...534-standalone-prevent-quick-upgrades.yaml | 32 --- ...ture-flag-by-default-for-Agent-8.11.0.yaml | 32 --- ...92-Prevent-multiple-stops-of-services.yaml | 32 --- .../1696319263-add-assetbeat-dependency.yaml | 32 --- .../1696361138-es-default-compression.yaml | 32 --- ...0758-bugfix-upgrade-progress-reporter.yaml | 32 --- ...nt-monitoring-metrics-interval-to-60s.yaml | 32 --- ...03197-updating_agentautodiscovery_811.yaml | 32 --- .../1697229987-Upgrade-to-Go-1.20.10.yaml | 32 --- ...-upgrade-elastic-agent-libs-to-v0.6.0.yaml | 32 --- ...restarts-on-failure-to-15s-on-Windows.yaml | 32 --- 19 files changed, 289 insertions(+), 543 deletions(-) create mode 100644 changelog/8.11.0.asciidoc create mode 100644 changelog/8.11.0.yaml delete mode 100644 changelog/fragments/1691060806-Processor-support-for-hints-autodiscover.yaml delete mode 100644 changelog/fragments/1693427183-install-progress.yaml delete mode 100644 changelog/fragments/1693813219-log-command-colors.yaml delete mode 100644 changelog/fragments/1693920861-netinfo-manifests.yaml delete mode 100644 changelog/fragments/1694187216-Uninstall-finds-and-kills-any-running-watcher-process.yaml delete mode 100644 changelog/fragments/1694439479-fix_creatork8sscript.yaml delete mode 100644 changelog/fragments/1695685534-standalone-prevent-quick-upgrades.yaml delete mode 100644 changelog/fragments/1695780865-Enable-tamper-protection-feature-flag-by-default-for-Agent-8.11.0.yaml delete mode 100644 changelog/fragments/1695920792-Prevent-multiple-stops-of-services.yaml delete mode 100644 changelog/fragments/1696319263-add-assetbeat-dependency.yaml delete mode 100644 changelog/fragments/1696361138-es-default-compression.yaml delete mode 100644 changelog/fragments/1696530758-bugfix-upgrade-progress-reporter.yaml delete mode 100644 changelog/fragments/1696955150-Slow-down-agent-monitoring-metrics-interval-to-60s.yaml delete mode 100644 changelog/fragments/1697103197-updating_agentautodiscovery_811.yaml delete mode 100644 changelog/fragments/1697229987-Upgrade-to-Go-1.20.10.yaml delete mode 100644 changelog/fragments/1697662109-upgrade-elastic-agent-libs-to-v0.6.0.yaml delete mode 100644 changelog/fragments/1698259940-Increase-wait-period-between-service-restarts-on-failure-to-15s-on-Windows.yaml diff --git a/changelog/8.11.0.asciidoc b/changelog/8.11.0.asciidoc new file mode 100644 index 00000000000..30f534fe478 --- /dev/null +++ b/changelog/8.11.0.asciidoc @@ -0,0 +1,107 @@ +// begin 8.11.0 relnotes + +[[release-notes-8.11.0]] +== 8.11.0 + +Review important information about the 8.11.0 release. + +[discrete] +[[security-updates-8.11.0]] +=== Security updates + + +elastic-agent:: + +* Upgrade To Go 1.20.10. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3601[#https://github.com/elastic/elastic-agent/pull/3601] + +[discrete] +[[breaking-changes-8.11.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 + +all:: + +[discrete] +[[breaking-https://github.com/elastic/beats/pull/36681]] +.Enable Compression By Default For Elasticsearch Outputs. {all-pull}https://github.com/elastic/beats/pull/36681[#https://github.com/elastic/beats/pull/36681] {all-issue}https://github.com/elastic/ingest-dev/issues/2458[#https://github.com/elastic/ingest-dev/issues/2458] +[%collapsible] +==== +The default compression level for Elasticsearch outputs is changing from 0 to 1. On typical workloads this is expected to decrease network data volume by 70-80%, while increasing cpu use by 20-25% and ingestion time by 10%. The previous behavior can be restored by adding 'compression_level: 0' to the output configuration. +==== +elastic-agent:: + +[discrete] +[[breaking-https://github.com/elastic/elastic-agent/pull/3593]] +.Elastic-Agent-Autodiscover To V0.6.4. Disables Metadata For Deployment And Cronjob. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3593[#https://github.com/elastic/elastic-agent/pull/3593] +[%collapsible] +==== +Elastic-agent-autodiscover library by default comes with add_resource_metadata.deployment=false and add_resource_metadata.cronjob=false. Pods that will be created from deployments or cronjobs will not have the extra metadata field for kubernetes.deployment or kubernetes.cronjob respectively. +==== + + + + + +[discrete] +[[new-features-8.11.0]] +=== New features + +The 8.11.0 release adds the following new and notable features. + + + + +* Enable Tamper Protection Feature Flag By Default For Elastic Agent Version 8.11.0. {-pull}https://github.com/elastic/elastic-agent/pull/3478[#https://github.com/elastic/elastic-agent/pull/3478] +CLI:: + +* Add Colors To Agent Messages Printed By The Elastic-Agent Logs Command Based On Their Level. {CLI-pull}https://github.com/elastic/elastic-agent/pull/3345[#https://github.com/elastic/elastic-agent/pull/3345] +elastic-agent:: + +* Add Support For Processors In Hints-Based Kubernetes Autodiscover. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3107[#https://github.com/elastic/elastic-agent/pull/3107] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/2959[#https://github.com/elastic/elastic-agent/issues/2959] +* Print Out Elastic Agent Installation Steps To Show Progress. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3338[#https://github.com/elastic/elastic-agent/pull/3338] + + +[discrete] +[[enhancements-8.11.0]] +=== Enhancements + + + + +* Fix The Kubernetes `Deploy/Kubernetes/Creator_k8.sh` Script To Correcly Exclude Configmaps. {-pull}https://github.com/elastic/elastic-agent/pull/3396[#https://github.com/elastic/elastic-agent/pull/3396] +elastic-agent:: + +* Support The Netinfo Variable In Elastic Kubernetes Manifests. Setting A New Environmental Variable `Elastic_netinfo=False` Globally Disables The `Netinfo.enabled` Parameter Of The `Add_host_metadata` Processor. This Disables The Indexing Of `Host.ip` And `Host.mac` Fields. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3354[#https://github.com/elastic/elastic-agent/pull/3354] +monitoring:: + +* Increase Agent Monitoring Metrics Interval From 10S To 60S To Reduce The Default Ingestion Load And Long Term Storage Requirements. {monitoring-pull}https://github.com/elastic/elastic-agent/pull/3578[#https://github.com/elastic/elastic-agent/pull/3578] + + + + +[discrete] +[[bug-fixes-8.11.0]] +=== Bug fixes + + + + +* The Elastic Agent Uninstall Process Now Finds And Kills Any Running Upgrade Watcher Process. Uninstalls Initiated Within 10 Minutes Of A Previous Upgrade Now Work As Expected. {-pull}https://github.com/elastic/elastic-agent/pull/3384[#https://github.com/elastic/elastic-agent/pull/3384] {-issue}https://github.com/elastic/elastic-agent/issues/3371[#https://github.com/elastic/elastic-agent/issues/3371] +agent:: + +* Upgrade `Elastic-Agent-Libs` To V0.6.0 To Fix The Agent Windows Service Becoming Unresponsive. Fixes Windows Service Timeouts During Wmi Queries And During Service Shutdown. {agent-pull}https://github.com/elastic/elastic-agent/pull/3632[#https://github.com/elastic/elastic-agent/pull/3632] +elastic-agent:: + +* Prevent A Standalone Elastic Agent From Being Upgraded If An Upgrade Is Already In Progress. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3473[#https://github.com/elastic/elastic-agent/pull/3473] {elastic-agent-issue}https://github.com/elastic/elastic-agent/issues/2706[#https://github.com/elastic/elastic-agent/issues/2706] +* Fix A Bug That Affected Reporting Progress Of The Agent Artifact Download During An Upgrade. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3548[#https://github.com/elastic/elastic-agent/pull/3548] +* Increase Wait Period Between Service Restarts On Failure To 15S On Windows. {elastic-agent-pull}https://github.com/elastic/elastic-agent/pull/3657[#https://github.com/elastic/elastic-agent/pull/3657] +runtime:: + +* Prevent Multiple Attempts To Stop An Already Stopped Service. {runtime-pull}https://github.com/elastic/elastic-agent/pull/3482[#https://github.com/elastic/elastic-agent/pull/3482] + +// end 8.11.0 relnotes diff --git a/changelog/8.11.0.yaml b/changelog/8.11.0.yaml new file mode 100644 index 00000000000..b20c71f12e7 --- /dev/null +++ b/changelog/8.11.0.yaml @@ -0,0 +1,182 @@ +version: 8.11.0 +entries: + - kind: feature + summary: Add support for processors in hints-based Kubernetes autodiscover. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3107 + issue: + - https://github.com/elastic/elastic-agent/issues/2959 + timestamp: 1691060806 + file: + name: 1691060806-Processor-support-for-hints-autodiscover.yaml + checksum: c55b54ba6747d5ac659649fd4e4a16e941364f8e + - kind: feature + summary: Print out Elastic Agent installation steps to show progress. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3338 + issue: [] + timestamp: 1693427183 + file: + name: 1693427183-install-progress.yaml + checksum: fb4c231a3a23abd6be758a4342484d10ce73aa6c + - kind: feature + summary: Add colors to Agent messages printed by the elastic-agent logs command based on their level. + description: "" + component: CLI + pr: + - https://github.com/elastic/elastic-agent/pull/3345 + issue: [] + timestamp: 1693813219 + file: + name: 1693813219-log-command-colors.yaml + checksum: 53b5a44c3799fa9888ad7beba34c2858bca7b3e2 + - kind: enhancement + summary: Support the NETINFO variable in Elastic Kubernetes manifests. Setting a new environmental variable `ELASTIC_NETINFO=false` globally disables the `netinfo.enabled` parameter of the `add_host_metadata` processor. This disables the indexing of `host.ip` and `host.mac` fields. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3354 + issue: [] + timestamp: 1693920861 + file: + name: 1693920861-netinfo-manifests.yaml + checksum: e9e5a459e64a189b7b74f5689c57d41d4fbf442c + - kind: bug-fix + summary: The Elastic Agent uninstall process now finds and kills any running upgrade Watcher process. Uninstalls initiated within 10 minutes of a previous upgrade now work as expected. + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/3384 + issue: + - https://github.com/elastic/elastic-agent/issues/3371 + timestamp: 1694187216 + file: + name: 1694187216-Uninstall-finds-and-kills-any-running-watcher-process.yaml + checksum: 31df28d9490d0c844b88d48f1aa3504cce2365ee + - kind: enhancement + summary: Fix the Kubernetes `deploy/kubernetes/creator_k8.sh` script to correcly exclude configmaps. + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/3396 + issue: [] + timestamp: 1694439479 + file: + name: 1694439479-fix_creatork8sscript.yaml + checksum: c65f7e65ebac64f9332a407f2449c88e30bd4239 + - kind: bug-fix + summary: Prevent a standalone Elastic Agent from being upgraded if an upgrade is already in progress. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3473 + issue: + - https://github.com/elastic/elastic-agent/issues/2706 + timestamp: 1695685534 + file: + name: 1695685534-standalone-prevent-quick-upgrades.yaml + checksum: 9df813abbdf5ae1558b16b1052a5bbc238cf7ae1 + - kind: feature + summary: Enable tamper protection feature flag by default for Elastic Agent version 8.11.0. + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/3478 + issue: [] + timestamp: 1695780865 + file: + name: 1695780865-Enable-tamper-protection-feature-flag-by-default-for-Agent-8.11.0.yaml + checksum: 46eac90f4af827db837fc7d19c1131328b011952 + - kind: bug-fix + summary: Prevent multiple attempts to stop an already stopped service. + description: "" + component: runtime + pr: + - https://github.com/elastic/elastic-agent/pull/3482 + issue: [] + timestamp: 1695920792 + file: + name: 1695920792-Prevent-multiple-stops-of-services.yaml + checksum: 8a0b54855b27c98e6af3d60df1c9cb04f935efee + - kind: breaking-change + summary: Enable compression by default for Elasticsearch outputs + description: 'The default compression level for Elasticsearch outputs is changing from 0 to 1. On typical workloads this is expected to decrease network data volume by 70-80%, while increasing cpu use by 20-25% and ingestion time by 10%. The previous behavior can be restored by adding ''compression_level: 0'' to the output configuration.' + component: all + pr: + - https://github.com/elastic/beats/pull/36681 + issue: + - https://github.com/elastic/ingest-dev/issues/2458 + timestamp: 1696361138 + file: + name: 1696361138-es-default-compression.yaml + checksum: f3bee390b1af6bc5049315e25e5c14d0ff23240e + - kind: bug-fix + summary: Fix a bug that affected reporting progress of the Agent artifact download during an upgrade. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3548 + issue: [] + timestamp: 1696530758 + file: + name: 1696530758-bugfix-upgrade-progress-reporter.yaml + checksum: a168f2ab2a26e7813bb230b5f663ecbeca9d624c + - kind: enhancement + summary: Increase Agent monitoring metrics interval from 10s to 60s to reduce the default ingestion load and long term storage requirements. + description: "" + component: monitoring + pr: + - https://github.com/elastic/elastic-agent/pull/3578 + issue: [] + timestamp: 1696955150 + file: + name: 1696955150-Slow-down-agent-monitoring-metrics-interval-to-60s.yaml + checksum: ead85ab471d5a6f609c367d57817d1c2299d93f2 + - kind: breaking-change + summary: Elastic-agent-autodiscover to v0.6.4. Disables metadata for deployment and cronjob + description: Elastic-agent-autodiscover library by default comes with add_resource_metadata.deployment=false and add_resource_metadata.cronjob=false. Pods that will be created from deployments or cronjobs will not have the extra metadata field for kubernetes.deployment or kubernetes.cronjob respectively. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3593 + issue: [] + timestamp: 1697103197 + file: + name: 1697103197-updating_agentautodiscovery_811.yaml + checksum: b937c2a635860c3497502b018b8b997143ba5fc3 + - kind: security + summary: Upgrade to Go 1.20.10. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3601 + issue: [] + timestamp: 1697229987 + file: + name: 1697229987-Upgrade-to-Go-1.20.10.yaml + checksum: e31fa72a840bb0616000830d86a3b18f1a22aae6 + - kind: bug-fix + summary: Upgrade `elastic-agent-libs` to v0.6.0 to fix the Agent Windows service becoming unresponsive. Fixes Windows service timeouts during WMI queries and during service shutdown. + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/3632 + issue: [] + timestamp: 1697662109 + file: + name: 1697662109-upgrade-elastic-agent-libs-to-v0.6.0.yaml + checksum: 70d3e8469fce838d73781c409d9dd7592adbddc8 + - kind: bug-fix + summary: Increase wait period between service restarts on failure to 15s on Windows. + description: This is the same value used by other Elastic windows services like endpoint-security. + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/3657 + issue: [] + timestamp: 1698259940 + file: + name: 1698259940-Increase-wait-period-between-service-restarts-on-failure-to-15s-on-Windows.yaml + checksum: 12985bc12758581d4f236ebf0928fde307ffceca diff --git a/changelog/fragments/1691060806-Processor-support-for-hints-autodiscover.yaml b/changelog/fragments/1691060806-Processor-support-for-hints-autodiscover.yaml deleted file mode 100644 index 0bed8190838..00000000000 --- a/changelog/fragments/1691060806-Processor-support-for-hints-autodiscover.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 support for processors in hints' based k8s autodiscover - -# 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/3107 - -# 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/2959 diff --git a/changelog/fragments/1693427183-install-progress.yaml b/changelog/fragments/1693427183-install-progress.yaml deleted file mode 100644 index 1725e9e40f1..00000000000 --- a/changelog/fragments/1693427183-install-progress.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: Print out Elastic Agent installation steps to show progress - -# 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/3338 - -# 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/1693813219-log-command-colors.yaml b/changelog/fragments/1693813219-log-command-colors.yaml deleted file mode 100644 index cdd5e34a369..00000000000 --- a/changelog/fragments/1693813219-log-command-colors.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: Add colors for log messages based on their level - -# 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: CLI -# 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/1693920861-netinfo-manifests.yaml b/changelog/fragments/1693920861-netinfo-manifests.yaml deleted file mode 100644 index 9c167de170a..00000000000 --- a/changelog/fragments/1693920861-netinfo-manifests.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: Setting a new environmental variable ELASTIC_NETINFO=false globally disables the netinfo.enabled parameter of add_host_metadata processor. This disables the indexing of host.ip and host.mac fields. - -# 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/1694187216-Uninstall-finds-and-kills-any-running-watcher-process.yaml b/changelog/fragments/1694187216-Uninstall-finds-and-kills-any-running-watcher-process.yaml deleted file mode 100644 index 057cc06d33e..00000000000 --- a/changelog/fragments/1694187216-Uninstall-finds-and-kills-any-running-watcher-process.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: Uninstall finds and kills any running watcher 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: - -# 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/3384 - -# 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/3371 diff --git a/changelog/fragments/1694439479-fix_creatork8sscript.yaml b/changelog/fragments/1694439479-fix_creatork8sscript.yaml deleted file mode 100644 index 7f7a9d1fd95..00000000000 --- a/changelog/fragments/1694439479-fix_creatork8sscript.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 - -# Change summary; a 80ish characters long description of the change. -summary: Fixing deploy/kubernetes/creator_k8.sh script to correcly exclude configmaps - -# 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/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/1695685534-standalone-prevent-quick-upgrades.yaml b/changelog/fragments/1695685534-standalone-prevent-quick-upgrades.yaml deleted file mode 100644 index fffa59953be..00000000000 --- a/changelog/fragments/1695685534-standalone-prevent-quick-upgrades.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 a standalone Elastic Agent from being upgraded if an upgrade is already in progress. - -# 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/3473 - -# 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/2706 diff --git a/changelog/fragments/1695780865-Enable-tamper-protection-feature-flag-by-default-for-Agent-8.11.0.yaml b/changelog/fragments/1695780865-Enable-tamper-protection-feature-flag-by-default-for-Agent-8.11.0.yaml deleted file mode 100644 index 75a33566b4b..00000000000 --- a/changelog/fragments/1695780865-Enable-tamper-protection-feature-flag-by-default-for-Agent-8.11.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: Enable tamper protection feature flag by default for Agent 8.11.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; a word indicating the component this changeset affects. -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/3478 - -# 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/1695920792-Prevent-multiple-stops-of-services.yaml b/changelog/fragments/1695920792-Prevent-multiple-stops-of-services.yaml deleted file mode 100644 index e15f5d6e927..00000000000 --- a/changelog/fragments/1695920792-Prevent-multiple-stops-of-services.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 multiple attempts to stop an already stopped service - -# 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: runtime - -# 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/1696319263-add-assetbeat-dependency.yaml b/changelog/fragments/1696319263-add-assetbeat-dependency.yaml deleted file mode 100644 index ab428367953..00000000000 --- a/changelog/fragments/1696319263-add-assetbeat-dependency.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 assetbeat among the external dependencies needed to package Elastic 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/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/obs-infraobs-team/issues/1114 diff --git a/changelog/fragments/1696361138-es-default-compression.yaml b/changelog/fragments/1696361138-es-default-compression.yaml deleted file mode 100644 index 2323467e47f..00000000000 --- a/changelog/fragments/1696361138-es-default-compression.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: Enable compression by default for Elasticsearch 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: "The default compression level for Elasticsearch outputs is changing from 0 to 1. On typical workloads this is expected to decrease network data volume by 70-80%, while increasing cpu use by 20-25% and ingestion time by 10%. The previous behavior can be restored by adding 'compression_level: 0' to the output configuration." - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: all - -# 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/beats/pull/36681 - -# 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/2458 diff --git a/changelog/fragments/1696530758-bugfix-upgrade-progress-reporter.yaml b/changelog/fragments/1696530758-bugfix-upgrade-progress-reporter.yaml deleted file mode 100644 index d39f4fa2f41..00000000000 --- a/changelog/fragments/1696530758-bugfix-upgrade-progress-reporter.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: Periodically report progress of Elastic Agent artifact download during upgrade - -# 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/3548 - -# 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/1696955150-Slow-down-agent-monitoring-metrics-interval-to-60s.yaml b/changelog/fragments/1696955150-Slow-down-agent-monitoring-metrics-interval-to-60s.yaml deleted file mode 100644 index bf86933d97e..00000000000 --- a/changelog/fragments/1696955150-Slow-down-agent-monitoring-metrics-interval-to-60s.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: Increase agent monitoring metrics interval from 10s to 60s to reduce load - -# 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: monitoring - -# 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/1697103197-updating_agentautodiscovery_811.yaml b/changelog/fragments/1697103197-updating_agentautodiscovery_811.yaml deleted file mode 100644 index 7837ea71eeb..00000000000 --- a/changelog/fragments/1697103197-updating_agentautodiscovery_811.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: Elastic-agent-autodiscover to v0.6.4. Disables metadata for deployment and cronjob - -# 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: Elastic-agent-autodiscover library by default comes with add_resource_metadata.deployment=false and add_resource_metadata.cronjob=false. Pods that will be created from deployments or cronjobs will not have the extra metadata field for kubernetes.deployment or kubernetes.cronjob respectively. - -# 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/3593 - -# 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/1697229987-Upgrade-to-Go-1.20.10.yaml b/changelog/fragments/1697229987-Upgrade-to-Go-1.20.10.yaml deleted file mode 100644 index ee447999639..00000000000 --- a/changelog/fragments/1697229987-Upgrade-to-Go-1.20.10.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.20.10. - -# 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/3601 - -# 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/1697662109-upgrade-elastic-agent-libs-to-v0.6.0.yaml b/changelog/fragments/1697662109-upgrade-elastic-agent-libs-to-v0.6.0.yaml deleted file mode 100644 index 192434f3b5c..00000000000 --- a/changelog/fragments/1697662109-upgrade-elastic-agent-libs-to-v0.6.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: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: upgrade elastic-agent-libs to v0.6.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: 'allows elastic-agent running as a windows service to receive more than one change request.' - -# Affected component; a word indicating the component this changeset affects. -component: 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/1698259940-Increase-wait-period-between-service-restarts-on-failure-to-15s-on-Windows.yaml b/changelog/fragments/1698259940-Increase-wait-period-between-service-restarts-on-failure-to-15s-on-Windows.yaml deleted file mode 100644 index d8c46d8e4dc..00000000000 --- a/changelog/fragments/1698259940-Increase-wait-period-between-service-restarts-on-failure-to-15s-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: Increase wait period between service restarts on failure to 15s 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: This is the same value used by other Elastic windows services like endpoint-security. - -# 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