CHANGELOG.md

<!-- This file is autogenerate, see CONTRIBUTING.md for instructions to add content. -->
# Changelog

<!-- For unreleased changes, see entries in .chloggen -->
<!-- next version -->

## [0.159.0] - 2026-08-28

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.159.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.159.0).

### 💡 Enhancements 💡

- `agent`: Add an opt-in file-log Logs-to-Metrics catalog using count and sum connectors. ([#2526](https://github.com/signalfx/splunk-otel-collector-chart/pull/2526))
  The feature is disabled by default and generated metrics are considered custom unless categorized otherwise.
  For configuration and cardinality guidance, see [Generate metrics from Kubernetes container logs](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#generate-metrics-from-kubernetes-container-logs).
  
- `chart`: Add `deployment.environment.name` to OpAMP Bridge descriptions when `environment` is set. ([#2569](https://github.com/signalfx/splunk-otel-collector-chart/pull/2569))
- `chart`: Add `remoteManagement.enabled` to deploy an OpAMP Bridge that manages chart-created collectors. ([#2548](https://github.com/signalfx/splunk-otel-collector-chart/pull/2548))
- `chart`: Bump obi to 0.12.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#2568](https://github.com/signalfx/splunk-otel-collector-chart/pull/2568),[#2572](https://github.com/signalfx/splunk-otel-collector-chart/pull/#2572))

## [0.158.0] - 2026-08-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.158.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.158.0).

### 🛑 Breaking changes 🛑

- `agent, clusterReceiver, gateway`: Use `deployment.environment.name` instead of the deprecated `deployment.environment` resource attribute. ([#2520](https://github.com/signalfx/splunk-otel-collector-chart/pull/2520))
  The optional `environment` value now adds `deployment.environment.name` to collected telemetry and Collector internal telemetry.
  To restore the deprecated name, see the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01570-to-01580)
  for details.
  
- `chart`: Remove the deprecated cert-manager subchart. ([#2533](https://github.com/signalfx/splunk-otel-collector-chart/pull/2533))
  cert-manager is no longer bundled with the Splunk OpenTelemetry Collector chart. Users with `certmanager.enabled=true` must migrate to a standalone cert-manager installation. Any saved `certmanager` values, including values under the legacy `cert-manager` schema key, must be removed before upgrading. See the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01570-to-01580) for migration details.
  
- `chart`: Rename all `resourcedetection` processor references to `resource_detection` ([#2529](https://github.com/signalfx/splunk-otel-collector-chart/pull/2529))
  The `resourcedetection` alias has been deprecated in favor of `resource_detection` in the chart-generated configuration.
  Any Helm values or overrides that reference `resourcedetection` (for example, `*.config.processors.resourcedetection`
  or pipelines that list `resourcedetection` as a processor) must be updated to use `resource_detection`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.
  

### 💡 Enhancements 💡

- `agent, clusterReceiver, gateway`: Add `deployment.environment.name` resource attribute to Collector internal telemetry when environment is configured. ([#2520](https://github.com/signalfx/splunk-otel-collector-chart/pull/2520))
- `gateway`: Enable SignalFx telemetry forwarding on port 9943 ([#2513](https://github.com/signalfx/splunk-otel-collector-chart/pull/2513))
  This adds a transparent HTTP forwarder for SignalFx exporters explicitly configured to use the gateway.
  It does not send requests through gateway service pipelines, so gateway processors are not applied.
  
- `operator`: Bump java-csa to v2.30.0 in helm-charts/splunk-otel-collector/values.yaml ([#2535](https://github.com/signalfx/splunk-otel-collector-chart/pull/2535))
- `operator`: Bump java to v2.30.0 in helm-charts/splunk-otel-collector/values.yaml ([#2534](https://github.com/signalfx/splunk-otel-collector-chart/pull/2534))
- `operator`: Bump operator to 0.120.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#2538](https://github.com/signalfx/splunk-otel-collector-chart/pull/2538))
- `operator`: Bump python-secureapp to v2.12.1-secureapp in helm-charts/splunk-otel-collector/values.yaml ([#2537](https://github.com/signalfx/splunk-otel-collector-chart/pull/2537))

### 🧰 Bug fixes 🧰

- `agent`: Fix `signalfx/histograms` exporter on agent to route through the gateway when gateway is enabled. ([#2553](https://github.com/signalfx/splunk-otel-collector-chart/pull/2553))
  When `gateway.enabled` and `featureGates.useControlPlaneMetricsHistogramData` are enabled, the agent's `signalfx/histograms` exporter now uses the gateway's SignalFx HTTP forwarder.
  Forwarded requests bypass the gateway metrics pipeline, so its processors are not applied.
  

## [0.157.0] - 2026-07-28

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.157.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.157.0).

### 🛑 Breaking changes 🛑

- `chart`: Rename all `kubeletstats` receiver references to `kubelet_stats` ([#2515](https://github.com/signalfx/splunk-otel-collector-chart/pull/2515))
  The `kubeletstats` alias has been deprecated in favor of `kubelet_stats` in the chart-generated configuration.
  Any Helm values or overrides that reference `kubeletstats` (for example, `*.config.receivers.kubeletstats`
  or pipelines that list `kubeletstats` as a receiver) must be updated to use `kubelet_stats`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.
  

### 💡 Enhancements 💡

- `agent`: Enable compaction by default for the persistent queue file storage extension. ([#79002](https://github.com/signalfx/splunk-otel-collector-chart/pull/79002))
  Prevents unbounded disk growth after traffic spikes. Compaction triggers when the file is ≥200 MiB and live data has dropped to ≤100 MiB and on collector start.
  Override configuration via `agent.config.extensions.file_storage/persistent_queue.compaction`.
  
- `chart`: Set mounted Splunk Secret files to mode `0440` by default and set `fsGroup: 999` on Linux Collector pods. Both settings remain configurable. ([#2441](https://github.com/signalfx/splunk-otel-collector-chart/pull/2441))
- `chart`: Add the Splunk access token header to the default OpAMP HTTP forwarder egress config. ([#4437](https://github.com/signalfx/splunk-otel-collector-chart/pull/4437))
- `chart`: Add an opt-in setting to read Splunk tokens from mounted Secret files. ([#2441](https://github.com/signalfx/splunk-otel-collector-chart/pull/2441))
  Enable `featureGates.mountSplunkSecretAsFile` to use this mode with either a chart-created or existing Secret. This option is disabled by default and is not currently supported with `distribution: gke/autopilot`.
  
- `chart`: Add `agent.tokenPassthrough` and `gateway.tokenPassthrough` options to enable passthrough of the client's authentication token to Splunk Observability and OpAMP. ([#2509](https://github.com/signalfx/splunk-otel-collector-chart/pull/2509))
  When enabled, the collector propagates the caller's `X-SF-Token` to Splunk Observability
  (via `headers_setter`) and to the OpAMP HTTP forwarder egress. Defaults preserve today's
  behavior: `agent.tokenPassthrough=false` and `gateway.tokenPassthrough=true`.
  
- `chart`: Bump TargetAllocator to 0.156.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2503](https://github.com/signalfx/splunk-otel-collector-chart/pull/2503))
- `chart`: Bump obi to 0.11.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2510](https://github.com/signalfx/splunk-otel-collector-chart/pull/2510))
- `operator`: Bump dotnet to v1.15.0 in helm-charts/splunk-otel-collector/values.yaml ([#2518](https://github.com/signalfx/splunk-otel-collector-chart/pull/2518))
- `operator`: Bump java-csa to v2.29.0 in helm-charts/splunk-otel-collector/values.yaml ([#2485](https://github.com/signalfx/splunk-otel-collector-chart/pull/2485))
- `operator`: Bump nodejs to v4.10.0 in helm-charts/splunk-otel-collector/values.yaml ([#2517](https://github.com/signalfx/splunk-otel-collector-chart/pull/2517))
- `operator`: Bump operator to 0.120.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2500](https://github.com/signalfx/splunk-otel-collector-chart/pull/2500))

### 🧰 Bug fixes 🧰

- `chart`: Allow original OpenTelemetry subchart names in values.schema.json validation. ([#2493](https://github.com/signalfx/splunk-otel-collector-chart/pull/2493))
- `chart`: Pin Linux-only workloads to Linux nodes, disable service account token mounting for the secret validation hook, and reject Windows workloads on EKS Fargate. ([#2522](https://github.com/signalfx/splunk-otel-collector-chart/pull/2522))

## [0.156.0] - 2026-07-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.156.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.156.0).

### 💡 Enhancements 💡

- `clusterReceiver`: Enable collection of NetworkPolicy and CustomResourceDefinition objects by default via k8s_objects pipeline. ([#4323](https://github.com/signalfx/splunk-otel-collector-chart/pull/4323))
  Added to the default `clusterReceiver.k8sObjects` list in pull mode (6h interval), with the
  required read permissions granted in the chart's ClusterRole.
  
  Collected only when a destination is enabled: `splunkPlatform.logsEnabled` (Splunk Platform logs)
  and/or `featureGates.sendK8sEventsToSplunkO11y` (Splunk Observability `/v3/event`); sent to each
  that is enabled. To opt out, remove these entries from `clusterReceiver.k8sObjects`.
  

## [0.155.0] - 2026-07-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.155.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.155.0).

### 🛑 Breaking changes 🛑

- `agent, clusterReceiver`: Change default of `splunkPlatform.disableCompression` from `true` to `false`, enabling gzip compression by default for HEC exporters. ([#2491](https://github.com/signalfx/splunk-otel-collector-chart/pull/2491))

### 🚩 Deprecations 🚩

- `chart`: Deprecate installing cert-manager as a subchart with `certmanager.enabled=true` ([#2451](https://github.com/signalfx/splunk-otel-collector-chart/pull/2451))
  Installing cert-manager through this chart will be removed in a future release. See the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01540-to-01550) for migration details.

### 💡 Enhancements 💡

- `agent, gateway`: Enrich SecureApp logs pipeline with Kubernetes metadata, resource detection, and environment attributes so that SecureApp events carry the same resource context as other log pipelines in the agent.
 ([#2480](https://github.com/signalfx/splunk-otel-collector-chart/pull/2480))
- `chart`: Enable block_on_overflow and improve no-drop logs pipeline reliability when featureGates.noDropLogsPipeline is enabled. ([#2488](https://github.com/signalfx/splunk-otel-collector-chart/pull/2488))
  Sets block_on_overflow: true on the exporter sending queue to apply backpressure to the filelog receiver when the queue is full, preventing data loss.
  The `queue_size` setting now counts individual log records instead of batches when `noDropLogsPipeline` is enabled.
  The default value of 1000 is automatically raised to a minimum of 10000 in this mode.
  For high-throughput workloads consider setting `splunkPlatform.sendingQueue.queueSize` significantly higher (e.g. 100000).
  
- `chart`: Bump TargetAllocator to 0.130.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2471](https://github.com/signalfx/splunk-otel-collector-chart/pull/2471))
- `chart`: Bump obi to 0.10.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2434](https://github.com/signalfx/splunk-otel-collector-chart/pull/2434),[#2496](https://github.com/signalfx/splunk-otel-collector-chart/pull/#2496))
- `gateway`: Add support for deploying the gateway as a StatefulSet, which allows users to use features like persistent storage. ([#2453](https://github.com/signalfx/splunk-otel-collector-chart/pull/2453))
  This change adds a new `gateway.mode` configuration option that can be set to `statefulset` to deploy the gateway as a StatefulSet instead of a Deployment.
  When `gateway.mode` is set to `statefulset`, users can also provide additional StatefulSet-specific configuration through the `gateway.statefulsetSpec` field.
  We also added support for a headless service when deploying the gateway as a StatefulSet, which can be enabled through the `gateway.headlessService.enabled` field.
  
- `operator`: Bump java to v2.29.0 in helm-charts/splunk-otel-collector/values.yaml ([#2475](https://github.com/signalfx/splunk-otel-collector-chart/pull/2475))
- `operator`: Bump nodejs to v4.9.0 in helm-charts/splunk-otel-collector/values.yaml ([#2472](https://github.com/signalfx/splunk-otel-collector-chart/pull/2472))
- `operator`: Bump operator to 0.117.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2478](https://github.com/signalfx/splunk-otel-collector-chart/pull/2478))

### 🧰 Bug fixes 🧰

- `agent`: Fix SecureApp log routing so that only logs from SecureApp-instrumented workloads are delivered to the SecureApp pipeline. Previously all OTLP logs could be incorrectly routed to the SecureApp pipeline when secureAppEnabled was true with logs or profiling disabled.
 ([#2457](https://github.com/signalfx/splunk-otel-collector-chart/pull/2457))

## [0.154.0] - 2026-06-16

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.154.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.154.0).

### 🛑 Breaking changes 🛑

- `agent, clusterReceiver, gateway`: Moved internal metrics resource attributes from `resource` processors to telemetry configuration. ([#2456](https://github.com/signalfx/splunk-otel-collector-chart/pull/2456))
  As part of this change, we removed the following processors as they were only used to set resource attributes on internal metrics:
  - `resource/add_mode` from the agent, clusterReceiver and gateway configurations
  - `resource/add_collector_k8s` from the clusterReceiver and gateway configuration
  
- `chart`: Use upstream [target allocator helm chart](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-target-allocator) as subchart instead of local custom configuration ([#2381](https://github.com/signalfx/splunk-otel-collector-chart/pull/2381))
  Please refer to the [upgrade guidelines from 0.153.1 to 0.154.0](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01531-to-01540)
  for more information. This change is only relevant when the
  target allocator is enabled.
  

### 💡 Enhancements 💡

- `clusterReceiver`: Add `featureGates.useEntityEventsForK8sProperties` to send Kubernetes entity updates through the signalfx entity events path. ([#2429](https://github.com/signalfx/splunk-otel-collector-chart/pull/2429))
- `operator`: When secureAppEnabled is set to true, the Instrumentation CR now activates SecureApp for Java (CSA image swap), Node.js (environment variable injection), and Python (secureapp variant image swap).
 ([#2455](https://github.com/signalfx/splunk-otel-collector-chart/pull/2455))
- `operator`: Bump nodejs to v4.8.0 in helm-charts/splunk-otel-collector/values.yaml ([#2450](https://github.com/signalfx/splunk-otel-collector-chart/pull/2450))
- `operator`: Bump operator to 0.115.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2461](https://github.com/signalfx/splunk-otel-collector-chart/pull/2461))

## [0.153.1] - 2026-06-01

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.153.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.153.0).

### 💡 Enhancements 💡

- `agent, gateway`: Remove `signalfx` exporter from trace pipelines ([#2432](https://github.com/signalfx/splunk-otel-collector-chart/pull/2432))
  The `signalfx` exporter is no longer required for trace correlation. Sending traces via OTLP will
  enable all trace correlation functionality.
  
- `opentelemetry-operator-crds`: Bump subchart opentelemetry-operator-crds to 0.0.7. Refer to further [instructions](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/charts/opentelemetry-operator-crds/README.md#upgrade-notes) for updating CRDs if using  option. ([#2436](https://github.com/signalfx/splunk-otel-collector-chart/pull/2436))
- `operator`: Bump operator to 0.114.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#2436](https://github.com/signalfx/splunk-otel-collector-chart/pull/2436))

## [0.153.0] - 2026-05-29

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.153.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.153.0).

### 🛑 Breaking changes 🛑

- `chart`: Change `splunk_app_name` in the `splunk_hec` exporter to `splunk-otel-collector-chart` ([#2426](https://github.com/signalfx/splunk-otel-collector-chart/pull/2426))
  The `splunk_app_name` reported by the Splunk HEC exporters changed from `splunk-otel-collector` to
  `splunk-otel-collector-chart`. This label serves for monitoring telemetry emitted by the chart.
  

### 💡 Enhancements 💡

- `agent, clusterReceiver, gateway`: Enable `include_resource_attributes` for the `opamp/splunk_o11y` extension. ([#2418](https://github.com/signalfx/splunk-otel-collector-chart/pull/2418))
  This change enables the `include_resource_attributes` configuration for the `opamp/splunk_o11y` component.
  Resource attributes collected from `service::telemetry::metrics` will now be included in the OpAMP exported data.
  Additionally, the telemetry resource configuration format is updated to v0.3.0.
  
- `chart`: Bump obi to 0.9.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2422](https://github.com/signalfx/splunk-otel-collector-chart/pull/2422))
- `operator`: Bump java to v2.28.0 in helm-charts/splunk-otel-collector/values.yaml ([#2427](https://github.com/signalfx/splunk-otel-collector-chart/pull/2427))
- `operator`: Bump nodejs to v4.7.2 in helm-charts/splunk-otel-collector/values.yaml ([#2421](https://github.com/signalfx/splunk-otel-collector-chart/pull/2421))

## [0.152.0] - 2026-05-14

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.152.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.152.0).

### 🛑 Breaking changes 🛑

- `agent`: Replace manual filelog container log parsing operators with a `container`-operator-based pipeline ([#2370](https://github.com/signalfx/splunk-otel-collector-chart/pull/2370))
  Replaces the manual `router` + `regex_parser`/`json_parser` + `recombine` chain for Docker/CRI-O/containerd log parsing with a simpler pipeline centered on the `container` operator.
  This pipeline provides format auto-detection, timestamp parsing, P/F log recombination, and k8s metadata extraction from the file path for both Linux and Windows nodes.
  
  The accepted value of `logsCollection.containers.containerRuntime` for CRI-O has changed from `cri-o` to `crio` to match the `container` operator's expected format.
  Users who have set `logsCollection.containers.containerRuntime: cri-o` must update their values to `crio`.
  
  Users of `logsCollection.containers.extraOperators` are affected: `attributes.log` is no longer available
  and must be replaced with `body`. Additionally, `attributes.time` is no longer set; use `timestamp` instead
  to access the log record's `Timestamp` field in stanza expressions.
  
  For full migration details see the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#container-log-parsing-now-uses-the-container-operator).
  
- `chart`: Rename all `hostmetrics` receiver references to `host_metrics` ([#2414](https://github.com/signalfx/splunk-otel-collector-chart/pull/2414))
  The `hostmetrics` alias has been deprecated in favor of `host_metrics` in the chart-generated configuration.
  Any Helm values or overrides that reference `hostmetrics` (for example, `*.config.receivers.hostmetrics`
  or pipelines that list `hostmetrics` as a receiver) must be updated to use `host_metrics`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.
  
- `chart`: Rename all `k8sobjects` receiver references to `k8s_objects` ([#2414](https://github.com/signalfx/splunk-otel-collector-chart/pull/2414))
  The `k8sobjects` alias has been deprecated in favor of `k8s_objects` in the chart-generated configuration.
  Any Helm values or overrides that reference `k8sobjects` (for example, `*.config.receivers.k8sobjects`
  or pipelines that list `k8sobjects` as a receiver) must be updated to use `k8s_objects`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.
  

### 💡 Enhancements 💡

- `agent`: Add `component: otel-collector-agent` to the agent DaemonSet's selector.matchLabels ([#2404](https://github.com/signalfx/splunk-otel-collector-chart/pull/2404))
  A new feature gate `featureGates.daemonSetComponentSelector` (disabled by default)
  adds `component: otel-collector-agent` to the agent DaemonSet's selector.
  To opt in, set
  `featureGates.daemonSetComponentSelector: true` and delete the DaemonSet before
  upgrading. See [UPGRADING.md](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#new-feature-gate-component-label-in-agent-daemonset-selector) for details.
  
- `chart`: Add OTLP log ingest option to send logs to Splunk Connect for OTLP instead of HEC ([#2392](https://github.com/signalfx/splunk-otel-collector-chart/pull/2392))
  For more information, see [Send logs to Splunk Platform with Splunk Connect for OTLP](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#send-logs-to-splunk-platform-with-splunk-connect-for-otlp).
  
- `chart`: Bump obi to 0.7.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#2371](https://github.com/signalfx/splunk-otel-collector-chart/pull/2371))
- `operator`: Bump nodejs to v4.7.1 in helm-charts/splunk-otel-collector/values.yaml ([#2378](https://github.com/signalfx/splunk-otel-collector-chart/pull/2378))

## [0.151.1] - 2026-05-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.151.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.151.0).

### 💡 Enhancements 💡

- `agent`: Add AWS Batch node taints to the default Collector agent tolerations list ([#2398](https://github.com/signalfx/splunk-otel-collector-chart/pull/2398))
  The default agent tolerations now include `batch.amazonaws.com/batch-node` for both
  `NoSchedule` and `NoExecute`, allowing the daemonset to run on AWS Batch-managed EKS nodes.
  

### 🧰 Bug fixes 🧰

- `operator`: Bump deprecated cert-manager subchart to [v1.19.5](https://github.com/cert-manager/cert-manager/releases/tag/v1.19.5) ([#2413](https://github.com/signalfx/splunk-otel-collector-chart/pull/2413))

## [0.151.0] - 2026-05-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.151.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.151.0).

### 🛑 Breaking changes 🛑

- `chart`: Rename all `filelog` receiver references to `file_log` ([#2396](https://github.com/signalfx/splunk-otel-collector-chart/pull/2396))
  The `filelog` alias has been deprecated in favor of `file_log` in the chart-generated configuration.
  Any Helm values or overrides that reference `filelog` (for example, `*.config.receivers.filelog`
  or pipelines that list `filelog` as a receiver) must be updated to use `file_log`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.
  

### 💡 Enhancements 💡

- `agent`: Add `port` option for etcd receivers to support non-standard etcd ports ([#2402](https://github.com/signalfx/splunk-otel-collector-chart/pull/2402))
  Set `agent.controlPlaneMetrics.etcd.port` to override the auto-detected default.
  
- `agent, clusterReceiver, gateway`: Add OpAMP extension support to the default agent, clusterReceiver and gateway configuration. ([#2406](https://github.com/signalfx/splunk-otel-collector-chart/pull/2406))
  The OpAMP extension is included in the default configuration but disabled by default behind a feature gate.
  Use the feature gate ID `splunk.opamp.enabled` to enable the OpAMP extension.
  Example:
  For the `agent`: `--set agent.featureGates=+splunk.opamp.enabled`
  For the `clusterReceiver`: `--set clusterReceiver.featureGates=+splunk.opamp.enabled`
  For the `gateway`: `--set gateway.featureGates=+splunk.opamp.enabled`
  
  Note: a new `http_forwarder` extension binds to port 4320 and forwards requests to Splunk O11y ingest.
  When running on the gateway, the extension is intended as a forwarding mechanism for sending data to the gateway from the agent and clusterReceiver.
  When running on the agent, the extension is intended as an entry point for receiving OpAMP data from instrumentation agents that support OpAMP, such as the Splunk OpenTelemetry Java agent.
  
- `operator`: Bump dotnet to v1.14.0 in helm-charts/splunk-otel-collector/values.yaml ([#2377](https://github.com/signalfx/splunk-otel-collector-chart/pull/2377))
- `operator`: Bump java to v2.27.0 in helm-charts/splunk-otel-collector/values.yaml ([#2391](https://github.com/signalfx/splunk-otel-collector-chart/pull/2391))

### 🧰 Bug fixes 🧰

- `agent`: Fix `prometheus/etcd` receiver to respect TLS secret and auto-detect scraping mode ([#2402](https://github.com/signalfx/splunk-otel-collector-chart/pull/2402))
  When a TLS secret was configured for etcd metrics, the `prometheus/etcd` receiver ignored it
  and still scraped port 2381 over plain HTTP. It now correctly uses the configured client
  certificates to scrape via mTLS. This fix applies to the `prometheus/etcd` receiver only
  (used when `featureGates.useControlPlaneMetricsHistogramData` is enabled, which is the default).
  
  Enabling etcd metrics no longer requires a TLS secret for environments that don't need
  mTLS (e.g. kubeadm defaults to HTTP on port 2381). See
  [Setting up etcd metrics](docs/advanced-configuration.md#setting-up-etcd-metrics) for details.
  

## [0.150.0] - 2026-04-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.150.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.150.0).

### 🛑 Breaking changes 🛑

- `chart`: Default API and ingest endpoints changed from `*.signalfx.com` to `*.observability.splunkcloud.com` ([#2364](https://github.com/signalfx/splunk-otel-collector-chart/pull/2364))
  The default endpoints have been updated as follows:
  - `https://ingest.<realm>.signalfx.com` → `https://ingest.<realm>.observability.splunkcloud.com`
  - `https://api.<realm>.signalfx.com` → `https://api.<realm>.observability.splunkcloud.com`

  The new endpoints resolve to different IP addresses. Review the
  [domain transition guide](https://help.splunk.com/en/splunk-observability-cloud/reference/splunk-observability-cloud-domain-transition-guide)
  for the full list of network and security controls to update before upgrading,
  or the collector will fail to send data.

  **To keep using the legacy `*.signalfx.com` endpoints**, set these values explicitly:
  ```yaml
  splunkObservability:
    ingestUrl: "https://ingest.<realm>.signalfx.com"
    apiUrl: "https://api.<realm>.signalfx.com"
  ```

- `agent`: Drop `server.address` and `server.port` dimensions from Prometheus metrics ([#2288](https://github.com/signalfx/splunk-otel-collector-chart/pull/2288))
  Prometheus metrics (especially coming from Istio) can run into dimension limits.
  To avoid data points being rejected due to exceeding the dimension limit, these
  dimensions will now be dropped when either `autodetect.prometheus` or `autodetect.istio`
  is enabled. Users may reference the data point attribute `service.instance.id` as an
  alternate source of the server address and port.


### 💡 Enhancements 💡

- `agent`: Add `maxUnmatchedBatchSize` option to `logsCollection.containers.multilineConfigs` ([#2379](https://github.com/signalfx/splunk-otel-collector-chart/pull/2379))
  The chart now supports `maxUnmatchedBatchSize` in `multilineConfigs`, which controls how many
  consecutive lines not matching `firstEntryRegex` are batched into a single log record.

- `gateway`: Add topologySpreadConstraints support for gateway deployment ([#2361](https://github.com/signalfx/splunk-otel-collector-chart/pull/2361))
  The gateway deployment now supports `gateway.topologySpreadConstraints` to control how
  gateway pods are distributed across topology domains (e.g., availability zones). When
  combined with `gateway.service.trafficDistribution` (`PreferSameZone` on Kubernetes 1.35+,
  or `PreferClose` on older versions), this enables zone-aware routing where clients prefer
  sending traffic to gateways in the same zone. Together, these options ensure gateways are
  evenly spread across zones while minimizing cross-AZ network traffic and costs.

- `agent`: Add resourcedetection processor to the agent logs/host pipeline ([#2385](https://github.com/signalfx/splunk-otel-collector-chart/pull/2385))
  The agent's `logs/host` pipeline was missing the `resourcedetection` processor, so
  journald system logs and extra file logs lacked cloud and host attributes
  (cloud.provider, host.id, host.name, etc.) that other agent log pipelines already
  included.

  This pipeline is rendered when `logsCollection.journald.enabled: true` or when
  `logsCollection.extraFileLogs` entries are defined. On distributions that support
  automatic cluster-name detection (EKS, GKE, OpenShift) with `clusterName` left
  unset, a second resource-detection instance is also added to automatically
  discover `k8s.cluster.name`.


### 🧰 Bug fixes 🧰

- `agent`: Fix histogram bucket count for `kubeproxy_network_programming_duration_seconds` metric ([#2328](https://github.com/signalfx/splunk-otel-collector-chart/pull/2328))
  Splunk Observability Cloud has a limit of 32 buckets for histograms. By default this histogram
  has more than 32 buckets, so the config will now merge buckets to meet the required limit
  to avoid this metric being dropped entirely. This change is relevant when both the
  `useControlPlaneMetricsHistogramData` feature gate and `agent.controlPlaneMetrics.proxy`
  config option are both enabled.

- `chart`: Add probes and scrapeconfigs RBAC permissions to Target Allocator ClusterRole ([#2359](https://github.com/signalfx/splunk-otel-collector-chart/pull/2359))
  The Target Allocator ClusterRole was missing permissions for `probes` and `scrapeconfigs`
  resources in the `monitoring.coreos.com` API group. This caused the allocator to fail with
  forbidden errors when attempting to list and watch these resources.

- `clusterReceiver`: Remove resourcedetection processor from cluster-scoped event and object pipelines ([#2369](https://github.com/signalfx/splunk-otel-collector-chart/pull/2369))
  The cluster receiver's `logs` (k8s_events), `logs/objects`, and `logs/events` pipelines
  previously used the `resourcedetection` processor, which added host and
  cloud-provider attributes (host.id, host.name, cloud.provider, cloud.platform,
  cloud.account.id, cloud.region, etc.) from the cluster receiver pod itself.
  These host-level attributes were misleading because cluster-scoped events and objects are not
  tied to any single host; they should reflect the cluster. These pipelines now only add `k8s.cluster.name`.
  A `host.name` resource attribute is still set to the node name of the cluster receiver pod (`K8S_NODE_NAME`)
  for use as the Splunk HEC `host` field.

- `gateway`: Add `profiling` to gateway OTLP port `enabled_for` lists ([#2365](https://github.com/signalfx/splunk-otel-collector-chart/pull/2365))
  The gateway OTLP ports (4317, 4318) were missing `profiling` in their `enabled_for`
  lists, unlike the agent ports which already included it. This meant the profiling signal
  alone could not enable the gateway OTLP ports.

- `operator`: Respect user-defined SPLUNK_PROFILER_ENABLED and SPLUNK_PROFILER_MEMORY_ENABLED in `instrumentation.spec.env` ([#2365](https://github.com/signalfx/splunk-otel-collector-chart/pull/2365))
  When `splunkObservability.profilingEnabled` is true, the chart auto-injects
  `SPLUNK_PROFILER_ENABLED=true` and `SPLUNK_PROFILER_MEMORY_ENABLED=true` into
  the Instrumentation CR. Previously, setting these to "false" in
  `instrumentation.spec.env` to globally disable profiling while keeping the
  pipeline active was silently overridden. The chart now correctly honors
  user-defined values and skips injection when they are already present.


## [0.149.0] - 2026-04-07

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.149.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.149.0).

### 🛑 Breaking changes 🛑

- `chart`: Rename all `k8sattributes` processor references to `k8s_attributes` ([#2326](https://github.com/signalfx/splunk-otel-collector-chart/pull/2326))
  The `k8sattributes` alias has been deprecated in favor of `k8s_attributes` in the chart-generated configuration.
  Any Helm values or overrides that reference `k8sattributes` (for example, `*.config.processors.k8sattributes`
  or pipelines that list `k8sattributes` as a processor) must be updated to use `k8s_attributes`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.

- `chart`: Rename all `otlp` exporter references to `otlp_grpc` ([#2326](https://github.com/signalfx/splunk-otel-collector-chart/pull/2326))
  The `otlp` alias has been deprecated in favor of `otlp_grpc` in the chart-generated configuration.
  Any Helm values or overrides that reference `otlp` (for example, `*.config.exporters.otlp`
  or pipelines that list `otlp` as an exporter) must be updated to use `otlp_grpc`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.

- `chart`: Rename all `otlphttp` exporter references to `otlp_http` ([#2326](https://github.com/signalfx/splunk-otel-collector-chart/pull/2326))
  The `otlphttp` alias has been deprecated in favor of `otlp_http` in the chart-generated configuration.
  Any Helm values or overrides that reference `otlphttp` (for example, `*.config.exporters.otlphttp`
  or pipelines that list `otlphttp` as an exporter) must be updated to use `otlp_http`.
  The chart will fail to be installed or upgraded if the deprecated alias is still referenced.


### 💡 Enhancements 💡

- `agent, clusterReceiver, gateway`: Add OpenShift resource detection support ([#2330](https://github.com/signalfx/splunk-otel-collector-chart/pull/2330))
  When distribution is set to "openshift", the openshift resource detector is now enabled
  in the resourcedetection processor. Previously, OpenShift clusters only had cloud-provider
  detectors (azure for cloudProvider=azure, gcp for cloudProvider=gcp) but no
  OpenShift-specific detector, and no detector at all for cloudProvider=aws (see the
  ec2 bug fix in this release). The openshift detector auto-discovers `k8s.cluster.name`,
  `cloud.provider`, `cloud.platform`, and `cloud.region` via the OpenShift API
  (`config.openshift.io/v1/infrastructures`). The `cloud.platform` value reflects the
  actual hosting environment (e.g., `aws_openshift`, `gcp_openshift`, `azure.openshift`).

  Cloud-provider-specific detectors remain enabled alongside the openshift detector to
  collect instance-level metadata: ec2 on AWS, gcp on GCP, and azure on Azure. The
  openshift detector is listed first to ensure the correct `cloud.platform` is set before
  cloud-provider detectors run.

  The `clusterName` Helm value is now optional for OpenShift (same as EKS and GKE). When
  not set, the openshift detector auto-discovers it from the cluster API. When explicitly
  set, the static value takes precedence.

- `chart`: Support all standard K8s probe fields (timeoutSeconds, periodSeconds, failureThreshold, successThreshold) in readinessProbe and livenessProbe configuration ([#2341](https://github.com/signalfx/splunk-otel-collector-chart/pull/2341))
  Previously only initialDelaySeconds was applied from readinessProbe and livenessProbe
  values. All other fields like timeoutSeconds were ignored. The probe templates
  now pass through all user-provided fields via toYaml.

- `chart`: Add configurable resource requests and limits for the Target Allocator container ([#2349](https://github.com/signalfx/splunk-otel-collector-chart/pull/2349))
  Users can now set `targetAllocator.resources` in values.yaml to configure CPU/memory
  requests and limits for the Target Allocator container.

- `chart`: Bump the OBI subchart to upstream opentelemetry-ebpf-instrumentation 0.6.0 ([#2300](https://github.com/signalfx/splunk-otel-collector-chart/pull/2300))
  Updates the vendored OBI dependency and rendered eBPF instrumentation example
  manifests to the upstream 0.6.0 chart release.

- `operator`: Bump operator to 0.109.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2347](https://github.com/signalfx/splunk-otel-collector-chart/pull/2347))

### 🧰 Bug fixes 🧰

- `agent, clusterReceiver, gateway`: Fix resource detection for non-EKS Kubernetes clusters on AWS ([#2330](https://github.com/signalfx/splunk-otel-collector-chart/pull/2330))
  For non-EKS Kubernetes clusters on AWS (cloudProvider=aws with distribution unset or
  set to openshift), EC2 instance metadata (host.id, cloud.account.id,
  cloud.availability_zone, etc.) was never collected. Two issues contributed to this:
  1. The chart used the eks detector, which only works on actual EKS clusters — it checks
     for EKS-specific signals (IRSA/Pod Identity token paths, OIDC issuer, Kubernetes
     version string) and returns an empty resource when those are absent. Switched to the
     ec2 detector, which works on any AWS instance with IMDS access.
  2. This code path only matched when distribution was unset (empty string), so OpenShift
     clusters on AWS (distribution=openshift, cloudProvider=aws) were excluded entirely.
     Broadened the condition to also match the openshift distribution.

- `clusterReceiver`: Set dnsPolicy to ClusterFirstWithHostNet for cluster receiver when clusterReceiver.hostNetwork is enabled ([#2348](https://github.com/signalfx/splunk-otel-collector-chart/pull/2348))
  When clusterReceiver.hostNetwork is enabled (e.g. for EKS Auto mode), the cluster receiver
  pod was unable to resolve in-cluster DNS names. Pods running with
  hostNetwork fall back to the node's DNS configuration unless dnsPolicy is explicitly set
  to ClusterFirstWithHostNet. This matches the existing daemonset behavior.


## [0.148.0] - 2026-03-26

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.148.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.148.0).

### 💡 Enhancements 💡

- `clusterReceiver`: Add feature gate to send Kubernetes entities to Splunk Observability v3/event endpoint ([#2284](https://github.com/signalfx/splunk-otel-collector-chart/pull/2284))
  When enabled via `featureGates.enableK8sEntities`, the cluster receiver routes
  Kubernetes entity data (from the k8s_cluster receiver) to the Splunk Observability
  /v3/event endpoint via otlphttp. Requires Splunk Observability configuration.
  This feature is experimental and may change or be removed in future releases.

- `operator`: Bump java to v2.26.1 in helm-charts/splunk-otel-collector/values.yaml ([#2299](https://github.com/signalfx/splunk-otel-collector-chart/pull/2299))

- `operator`: Bump nodejs to v4.4.0 in helm-charts/splunk-otel-collector/values.yaml ([#2276](https://github.com/signalfx/splunk-otel-collector-chart/pull/2276))

### 🧰 Bug fixes 🧰

- `config`: Updated default configuration to use dot-notation attributes for internal metrics,
  addressing the upstream change in ([#14815](https://github.com/open-telemetry/opentelemetry-collector/pull/14815))

- `agent`: Add configurable scrapeInterval for control plane Prometheus receivers and default to 10s ([#2302](https://github.com/signalfx/splunk-otel-collector-chart/pull/2302))
  The Prometheus receivers that replaced SmartAgent receivers for control plane components
  (apiserver, controller-manager, scheduler, proxy, coredns, etcd) were using the Prometheus
  default scrape interval of 60s instead of the SmartAgent default of 10s. A new
  `agent.controlPlaneMetrics.scrapeInterval` config option has been added (default: `10s`)
  to allow users to tune the interval. This also applies to the EKS apiserver metrics
  collected by the cluster receiver.

- `operator`: Fix instrumentation hook job ServiceAccount missing imagePullSecrets from image.imagePullSecrets ([#2321](https://github.com/signalfx/splunk-otel-collector-chart/pull/2321))
  When instrumentation.installationJob.enabled=true and image.imagePullSecrets is set,
  the dedicated ServiceAccount created for the hook job now receives the pull secrets,
  allowing the job's kubectl image to be pulled from a private registry.


## [0.147.1] - 2026-03-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.147.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.147.0).

### 🧰 Bug fixes 🧰

- `agent`, `clusterReceiver`, `gateway`: Remove reference to a removed Google Kubernetes Engine (GKE) attribute in the resource detection processor ([#2282](https://github.com/signalfx/splunk-otel-collector-chart/pull/2282))
  The `faas.id` attribute has been removed in favor of `faas.instance`. Referencing this
  attribute in the processor configuration was causing upgrades to fail in GKE environments
  when `clusterName` is not set in `values.yaml`.
- `agent`: Revert change in `v0.147.0` that dropped `destination_service_namespace` from Istio metric attributes ([#2279](https://github.com/signalfx/splunk-otel-collector-chart/pull/2279))

## [0.147.0] - 2026-03-10

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.147.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.147.0).

### ❗ Known Issues ❗

- `GKE`: This version is broken in GKE environments when `clusterName` is not set in `values.yaml`. For this distribution,
  please skip this release in favor of `v0.147.1`.

### 🛑 Breaking changes 🛑

- `operator`: Change default `operator.admissionWebhooks.autoGenerateCert.recreate` from `true` to `false`. ([#2261](https://github.com/signalfx/splunk-otel-collector-chart/pull/2261))
  The self-signed webhook certificate is now reused across helm upgrades instead of being
  regenerated every time. The default certificate validity is 10 years (certPeriodDays: 3650),
  so rotation per-upgrade is not required for most deployments.

  To restore the previous behavior (regenerate certificate on every upgrade), set:

  ```yaml
  operator:
    manager:
      rolling: true # recommended
    admissionWebhooks:
      autoGenerateCert:
        recreate: true
  ```

  Note: `manager.rolling: true` is recommended with `recreate: true` — it restarts the operator
  pod so it loads the new certificate promptly. Without it, there is a delay before the
  webhook server picks up the new cert, during which Instrumentation CR requests may fail
  with x509 errors.

- `agent`: Drop `destination_service_namespace` from Istio metric attributes ([#2275](https://github.com/signalfx/splunk-otel-collector-chart/pull/2275))
  Users running the chart with `autodetect` enabled have hit the dimension limit
  for Istio metrics. This fix drops the `destination_service_namespace` metric
  dimension to avoid hitting the dimension limit and dropping the data point entirely.


### 💡 Enhancements 💡

- `operator`: Add Job-based Instrumentation CR installation Job. ([#2261](https://github.com/signalfx/splunk-otel-collector-chart/pull/2261))
  The Instrumentation CR is deployed as a regular Helm resource by default. A new option
  `instrumentation.installationJob.enabled` deploys the CR via a Kubernetes Job that waits
  for webhook readiness before applying the CR, with built-in retry. This is the recommended
  option for Helm v4 or environments with slow operator startup.

  See [Auto-instrumentation Install](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/auto-instrumentation-install.md#instrumentation-cr-management) for details.


### 🧰 Bug fixes 🧰

- `eks_addon`: Fixed journald receiver issues in the EKS Add-on by mounting required shared library paths used by journalctl and aligning the directory structure with EKS node conventions. ([#2260](https://github.com/signalfx/splunk-otel-collector-chart/pull/2260))

## [0.146.0] - 2026-03-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.146.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.146.0).

### 💡 Enhancements 💡

- `clusterReceiver`: Add feature gate to send Kubernetes events to Splunk Observability /v3/event endpoint ([#2263](https://github.com/signalfx/splunk-otel-collector-chart/pull/2263))
  When enabled via `featureGates.sendK8sEventsToSplunkO11y`, the cluster receiver routes
  Kubernetes events to the Splunk Observability /v3/event endpoint with the
  `X-Splunk-Instrumentation-Library` header. Requires `clusterReceiver.eventsEnabled` and
  Splunk Observability configuration.

- `opentelemetry-operator-crds`: Bump subchart opentelemetry-operator-crds to 0.0.6. Refer to further [instructions](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/charts/opentelemetry-operator-crds/README.md#upgrade-notes) for updating CRDs if using  option. ([#2244](https://github.com/signalfx/splunk-otel-collector-chart/pull/2244))
- `operator`: Bump java to v2.25.1 in helm-charts/splunk-otel-collector/values.yaml ([#2258](https://github.com/signalfx/splunk-otel-collector-chart/pull/2258))
- `operator`: Bump operator to 0.106.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#2244](https://github.com/signalfx/splunk-otel-collector-chart/pull/2244))

## [0.145.1] - 2026-02-23

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.145.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.145.1).

### 💡 Enhancements 💡

- `agent, clusterReceiver`: Scrape `kubernetes_build_info` metric from Kubernetes apiserver ([#2216](https://github.com/signalfx/splunk-otel-collector-chart/pull/2216))
- `operator`: Bump java to v2.25.0 in helm-charts/splunk-otel-collector/values.yaml ([#2248](https://github.com/signalfx/splunk-otel-collector-chart/pull/2248))

## [0.145.0] - 2026-02-10

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.145.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.145.0).

### 💡 Enhancements 💡

- `operator`: Bump dotnet to v1.13.0 in helm-charts/splunk-otel-collector/values.yaml ([#2187](https://github.com/signalfx/splunk-otel-collector-chart/pull/2187))
- `operator`: Bump java to v2.24.0 in helm-charts/splunk-otel-collector/values.yaml ([#2177](https://github.com/signalfx/splunk-otel-collector-chart/pull/2177))
- `operator`: Bump nodejs to v4.3.0 in helm-charts/splunk-otel-collector/values.yaml ([#2098](https://github.com/signalfx/splunk-otel-collector-chart/pull/2098))

### 🧰 Bug fixes 🧰

- `agent`: Fix bug causing property updates to fail when the gateway is enabled ([#2234](https://github.com/signalfx/splunk-otel-collector-chart/pull/2234))
  The SignalFx exporter's property updates coming from the agent were failing to properly be
  sent when the gateway was enabled, due to a misconfigured realm value introduced in `v0.142.0`.


## [0.144.2] - 2026-02-05

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.144.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.144.0).

### 🧰 Bug fixes 🧰

- `agent`: Fix Prometheus autodetect metric filtering ([#2222](https://github.com/signalfx/splunk-otel-collector-chart/pull/2222))
  A [change](https://github.com/signalfx/splunk-otel-collector-chart/pull/2141) was introduced in `v0.138.0` that
  incorrectly set filters to only keep Istio and Envoy related metrics when `autodetect.prometheus` is enabled.
  The filtering should keep all Prometheus metrics and only filter when `autodetect.prometheus` is disabled, and
  `autodetect.istio` is enabled.


## [0.144.1] - 2026-02-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.144.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.144.0).

### 💡 Enhancements 💡

- `agent, clusterReceiver`: Add additional Kubernetes API server metrics ([#2223](https://github.com/signalfx/splunk-otel-collector-chart/pull/2223))
  Collect `apiserver_storage_size_bytes` and `apiserver_requested_deprecated_apis` metrics from the API server.


## [0.144.0] - 2026-02-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.144.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.144.0).

### 🛑 Breaking changes 🛑

- `gateway`: Remove `signalfx` receiver from gateway ([#2191](https://github.com/signalfx/splunk-otel-collector-chart/pull/2191))
  The `signalfx` receiver was removed from all default gateway pipelines in #2172. This change removes the
  receiver's declaration in the gateway config. If the `signalfx` receiver is still needed, the following
  section can be added to your values.yaml file:
  ```
  gateway:
    config:
      receivers:
        signalfx:
          endpoint: 0.0.0.0:9943
          include_metadata: true
    ports:
      signalfx:
        containerPort: 9943
        protocol: TCP
        enabled_for: [metrics, traces, logs]
  ```
  Please note that the `signalfx` receiver will eventually be deprecated and removed.


### 💡 Enhancements 💡

- `agent`: Enable `container.cpu.usage` metric by default ([#1962](https://github.com/signalfx/splunk-otel-collector-chart/pull/1962))
- `agent (logsCollection-journald)`: Allow users to configure the chart so the `journald` receiver can use the host's journalctl binary. ([#2211](https://github.com/signalfx/splunk-otel-collector-chart/pull/2211))
  To enable this, set the `logsCollection.journald.useHostJournalctl` option to true.
  By default, this option is false, so the collector uses the bundled journalctl binary.
  For more details, see [Advanced Configuration](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#use-the-host-journalctl-binary).


### 🧰 Bug fixes 🧰

- `agent`: Skip token passthrough if Splunk Observability is disabled ([#2219](https://github.com/signalfx/splunk-otel-collector-chart/pull/2219))

## [0.143.0] - 2026-01-14

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.143.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.143.0).

## [0.142.0] - 2026-01-14

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.142.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.142.0).

### 🛑 Breaking changes 🛑

- `agent, gateway`: Send metrics collected about the agent pod itself via OTLP from agent to the gateway ([#2172](https://github.com/signalfx/splunk-otel-collector-chart/pull/2172))
  Previously, metrics were being sent via SignalFx exporter to SignalFx receiver. This change removes
  the SignalFx receiver from the gateway's metric pipelines. The SignalFx receiver is on the path towards
  deprecation. The SignalFx exporter remains in the agent's `metrics` pipeline even when the gateway is enabled, but
  its only purpose is to sync host metadata, it does not send any metrics.

- `gateway`: Include metadata coming from connections to the OTLP receiver ([#2171](https://github.com/signalfx/splunk-otel-collector-chart/pull/2171))
  This is part of an effort to remove the `signalfx` receiver from the default gateway configuration. This change
  will allow access tokens to be passed from agents to the gateway through the OTLP receiver.
  To revert this change to previous behavior, please add the following to your `values.yaml` file:
  ```
  gateway:
    config:
      receivers:
        otlp:
          protocols:
            grpc:
              include_metadata: false
            http:
              include_metadata: false
  ```


### 🚀 New components 🚀

- `OBI subchart`: Add the OpenTelemetry eBPF Instrumentation sub-chart ([#2190](https://github.com/signalfx/splunk-otel-collector-chart/pull/2190))
  OpenTelemetry eBPF Instrumentation (OBI) is auto-instrumentation that generates trace and metric telemetry for your application using eBPF technology. OBI inspects application executables and the OS networking layer to automatically instrument network communication, application operation, and more.

  The OBI sub-chart deploys OBI as a daemonset within your Kubernetes cluster. All applications within your cluster that are not already instrumented with OpenTelemetry will be instrumented. See the OBI documentation on how to customize this.

  The OBI project, and this sub-chart, are still evolving. This functionality is in an alpha stage of release. Please direct any feedback or questions through Splunk support services.


### 💡 Enhancements 💡

- `gateway`: Make replicaCount optional for the gateway deployment to allow HPA to manage replicas without conflicts ([#2198](https://github.com/signalfx/splunk-otel-collector-chart/pull/2198))

## [0.141.0] - 2025-12-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.141.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.141.0).

### 🛑 Breaking changes 🛑

- `gateway`: Remove support for sending SignalFx events through the gateway ([#2170](https://github.com/signalfx/splunk-otel-collector-chart/pull/2170))
  Please send SignalFx events directly to Splunk Observability Cloud instead of through the gateway.
  This change will have no impact on users unless they've introduced custom behavior that sends
  events to the gateway.


### 🧰 Bug fixes 🧰

- `agent`: Fix k8sattributes processor incorrectly using host.name for pod association ([#2183](https://github.com/signalfx/splunk-otel-collector-chart/pull/2183))
  The k8sattributes processor was configured to use host.name as one of the pod association sources.
  However, the processor expects host.name to be a pod IP address, while our collector sets
  host.name to the k8s node name.


## [0.140.0] - 2025-11-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.140.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.140.0).

### 🧰 Bug fixes 🧰

- `agent`: Fix failed agent service creation when no ports are exposed. The agent k8s service is now only created when there are ports to expose ([#2166](https://github.com/signalfx/splunk-otel-collector-chart/pull/2166))

## [0.138.1] - 2025-11-07

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.138.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.138.0).

### 💡 Enhancements 💡

- `agent`: Update Istio autodetect rules. The detection logic has been expanded to identify Istio components more reliably. ([#2132](https://github.com/signalfx/splunk-otel-collector-chart/pull/2132))
  This change may impact billing, as the detection rules have been updated to be less restrictive.
  Metrics will now be scraped from istiod, Istio gateways, and Istio sidecars (`istio-proxy` containers.)
  Metrics were previously only being scraped from istiod.

- `agent`: Filter incoming metrics from Prometheus receiver when Istio autodetection is enabled. ([#2141](https://github.com/signalfx/splunk-otel-collector-chart/pull/2141))
  The `prometheus` receiver is now being used when `autodetect.istio: true` instead of `prometheus_simple`.
  The reason for this change is that the `prometheus` receiver supports filtering metrics being scraped by
  the receiver. Filtering has been introduced to only scrape metrics that are included in default content.

- `clusterReceiver`: Disabling attributes not needed for k8s cluster receiver metrics ([#2157](https://github.com/signalfx/splunk-otel-collector-chart/pull/2157))
  The following attributes have been disabled to reduce cardinality:
  - k8s.container.status.last_terminated_reason
  - k8s.hpa.scaletargetref.apiversion

- `clusterReceiver`: Enable k8sobjects for pods, in pull mode at 6h frequency ([#2147](https://github.com/signalfx/splunk-otel-collector-chart/pull/2147))
- `clusterReceiver`: Added k8s.pod.qos_class ([#2144](https://github.com/signalfx/splunk-otel-collector-chart/pull/2144))
- `clusterReceiver`: Enable metrics (k8s.container.status.reason, k8s.pod.status_reason, k8s.node.condition) for cluster receiver ([#2151](https://github.com/signalfx/splunk-otel-collector-chart/pull/2151))
  Enable the following metrics by default in K8s cluster receiver configuration:
  * [k8s.container.status.reason](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/k8sclusterreceiver/documentation.md#k8scontainerstatusreason): this metric gets containers in `CrashLoopBackOff`, `ImagePullBackOff` state, for example, using k8s.container.status.reason attribute.
  * [k8s.node.condition](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/k8sclusterreceiver/documentation.md#k8snodecondition): this metrics gets Nodes in `MemoryPressure`, for example, with condition attribute
  * [k8s.pod.status_reason](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/k8sclusterreceiver/documentation.md#k8spodstatus_reason): this metric helps detect Pods in status `Evicted`, for example

- `operator`: Add support for `instrumentation.spec.defaults` field in Helm values to configure default instrumentation behavior. ([#2152](https://github.com/signalfx/splunk-otel-collector-chart/pull/2152))
  Users can now configure the `defaults.useLabelsForResourceAttributes` option via Helm values, allowing
  Kubernetes labels (e.g., `app.kubernetes.io/name`, `app.kubernetes.io/version`) to be used as resource attributes
  in auto-instrumented applications. Read more [here](https://github.com/open-telemetry/opentelemetry-operator/blob/v0.138.0/README.md#configure-resource-attributes-with-labels).

  Example usage:
  ```yaml
  instrumentation:
    spec:
      defaults:
        useLabelsForResourceAttributes: true
  ```


### 🧰 Bug fixes 🧰

- `agent`: Fix kubeletstats receiver failing on GKE Autopilot clusters running Kubernetes 1.32+ ([#2159](https://github.com/signalfx/splunk-otel-collector-chart/pull/2159))
  - GKE Autopilot clusters running k8s 1.32+ disable the insecure kubelet read-only port (10255) by default.
  - The receiver in GKE Autopilot now uses the secure kubelet endpoint (port 10250) with serviceAccount authentication.
  - Add RBAC permissions to ClusterRole for restricted nodes/pods endpoint in GKE Autopilot


## [0.138.0] - 2025-10-29

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.138.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.138.0).

### 🛑 Breaking changes 🛑

- `chart`: Remove fluentd sidecar container and related configuration options ([#2138](https://github.com/signalfx/splunk-otel-collector-chart/pull/2138))
  The legacy fluentd sidecar container has been removed from the chart. All users should now use the native
  OpenTelemetry logs collection, which is the default and provides better performance and resource efficiency.
  If you still need to use fluentd for log collection, you can run it as a separate deployment using the
  official fluentd helm chart and forward logs to the collector using the fluentforward receiver.
  See the [upgrade guide](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01370-to-01380)
  for detailed instructions.

## [0.137.0] - 2025-10-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.137.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.137.0).

### 🛑 Breaking changes 🛑

- `agent`: Remove `signalfx` receiver from the default agent configuration ([#2120](https://github.com/signalfx/splunk-otel-collector-chart/pull/2120))
  This change affects the metrics pipeline only. Data should be sent to the agent in the OTLP format instead of SignalFx.
  If the `signalfx` receiver is still needed, the following section can be added to your `values.yaml` file:
  ```
  agent:
    config:
      receivers:
        signalfx:
          endpoint: 0.0.0.0:9943
    ports:
      signalfx:
        containerPort: 9943
        hostPort: 9943
        protocol: TCP
        enabled_for: [metrics]
  ```
  Please note that the `signalfx` receiver will eventually be deprecated and removed.

### 💡 Enhancements 💡

- `agent`: Bind the OTLP HTTP port 4318 to the host network ([#2102](https://github.com/signalfx/splunk-otel-collector-chart/pull/2102))
  This change is effective only for Windows nodes, where the port binding was previously missing.
  For Linux nodes, the hostNetwork setting already ensures the port is bound, so no change in behavior should occur for default chart config.

- `agent`: Configuration changes to support Secure Application features in Splunk Observability Cloud ([#2106](https://github.com/signalfx/splunk-otel-collector-chart/pull/2106))
- `chart`: Move deprecated Istio pod annotation to pod label ([#2108](https://github.com/signalfx/splunk-otel-collector-chart/pull/2108))
  The `sidecar.istio.io/inject` [annotation](https://istio.io/latest/docs/reference/config/annotations/#SidecarInject)
  has been deprecated in favor of the [label](https://istio.io/latest/docs/reference/config/labels/#SidecarInject)
  with the same name.

- `clusterReceiver`: Enable additional attributes (k8s.kubelet.version) for k8s cluster receiver ([#2103](https://github.com/signalfx/splunk-otel-collector-chart/pull/2103))
- `clusterReceiver`: Added k8s.hpa.scaletargetref.{api_version,kind,name} resource attributes, plus transform logic mapping HPA scaleTargetRef to workload (replicaset/statefulset/deployment) names in the Kubernetes cluster receiver configuration ([#2126](https://github.com/signalfx/splunk-otel-collector-chart/pull/2126))
- `gateway`: Replace `access_token_passthrough` with `include_metadata` in the gateway configuration. This change follows the removal of `access_token_passthrough` from the `signalfx` receiver and maintains the previous functionality of forwarding the access token. ([#2122](https://github.com/signalfx/splunk-otel-collector-chart/pull/2122))
- `gateway`: Configuration changes to support Secure Application features in Splunk Observability Cloud ([#2128](https://github.com/signalfx/splunk-otel-collector-chart/pull/2128))
- `operator`: Use [splunk-otel-instrumentation-python](quay.io/signalfx/splunk-otel-instrumentation-python) image for auto-instrumentation of Python applications with the operator. ([#1965](https://github.com/signalfx/splunk-otel-collector-chart/pull/1965))
  - To use a different image for Python auto-instrumentation, set the configuration option `instrumentation.python.image`.

- `operator`: Bump java to v2.20.1 in helm-charts/splunk-otel-collector/values.yaml ([#2070](https://github.com/signalfx/splunk-otel-collector-chart/pull/2070))

### 🧰 Bug fixes 🧰

- `agent`: Fix agent configuration when metrics are disabled for Splunk O11y Cloud ([#2083](https://github.com/signalfx/splunk-otel-collector-chart/pull/2083))
  Some functionality should not be configured for the agent when metrics are disabled,
  as it causes the agent to crash on startup.

- `chart`: Fix creation of validateSecret image name to use correct image configuration values ([#2123](https://github.com/signalfx/splunk-otel-collector-chart/pull/2123))

## [0.136.0] - 2025-10-02

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.136.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.136.1).

### 🛑 Breaking changes 🛑

- `clusterReceiver`: Remove the `k8sattributesprocessor` from the `clusterReceiver` logs pipeline to fix incorrect enrichment of Kubernetes object and event data. ([#2075](https://github.com/signalfx/splunk-otel-collector-chart/pull/2075))
  - The `k8sattributesprocessor` was previously misconfigured in the `clusterReceiver` pipeline, resulting in all Kubernetes objects and events being enriched with pod metadata, even when it was not appropriate.
  - This led to incorrect and non-deterministic `k8s.pod.*` attributes being added to objects and events, such as enriching non-pod objects with pod fields.
  - After this change:
    - Events from the `k8s_events` receiver will no longer include `container.id`, `container.image.name`, and `container.image.tag` attributes.
    - Events from the `k8sobjects` receiver will no longer have any `k8s.pod.*` or `container.*` attributes except `k8s.namespace.name` (when applicable) and `k8s.resource.name`
  - This restores correct and predictable enrichment, and eliminates misleading data.
  - If your downstream systems or dashboards depend on the removed attributes, please update them accordingly.


### 💡 Enhancements 💡

- `opentelemetry-operator-crds`: Bump subchart opentelemetry-operator-crds to 0.0.5. Refer to further [instructions](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/charts/opentelemetry-operator-crds/README.md#upgrade-notes) for updating CRDs if using  option. ([#2091](https://github.com/signalfx/splunk-otel-collector-chart/pull/2091))
- `operator`: Bump operator to 0.95.3 in helm-charts/splunk-otel-collector/Chart.yaml ([#2091](https://github.com/signalfx/splunk-otel-collector-chart/pull/2091))

### 🧰 Bug fixes 🧰

- `agent`: Skip os-release mount for GKE ([#2089](https://github.com/signalfx/splunk-otel-collector-chart/pull/2089))

## [0.135.0] - 2025-09-25

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.135.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.135.0).

### 🛑 Breaking changes 🛑

- `all`: Update labels in all resources ([#2027](https://github.com/signalfx/splunk-otel-collector-chart/pull/2027))
  - Remove "heritage" label from all objects managed by the chart
  - Set all "app.kubernetes.io/managed-by" labels to "Helm"

- `agent`: Remove `splunkObservability.logsEnabled` option ([#2058](https://github.com/signalfx/splunk-otel-collector-chart/pull/2058))
  Logs cannot be sent directly to Splunk Observability anymore.
  Configure `splunkPlatform` to send logs to Splunk Platform and enable Log Observer Connect to view the logs in Splunk Observability.
  See the following documentation for more details: https://help.splunk.com/en/splunk-observability-cloud/manage-data/view-splunk-platform-logs/accomplish-logs-pipeline-rules-in-splunk-platform


### 💡 Enhancements 💡

- `chart`: Adds configuration option for Splunk Platform metrics sourcetype ([#1941](https://github.com/signalfx/splunk-otel-collector-chart/pull/1941))
  - Users can override the metrics sourcetype for Splunk Platform using the `splunk.com/metricsSourcetype` annotation or the `.Values.splunkPlatform.metricsSourcetype` Helm value.
  - See `advanced-configuration.md` for detailed precedence and usage notes.


### 🧰 Bug fixes 🧰

- `log`: Update `sending_queue` batch settings when `noDropLogsPipeline` is enabled ([#2076](https://github.com/signalfx/splunk-otel-collector-chart/pull/2076))

## [0.134.0] - 2025-09-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.134.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.134.0).

### 🛑 Breaking changes 🛑

- `instrumentation`: Reduce Java and .Net auto-instrumentation resource attributes ([#2006](https://github.com/signalfx/splunk-otel-collector-chart/pull/2006))
  This change limits the resource attributes added to the telemetry data emitted by Java and .Net instrumentation libraries to the attributes generated by the `Container` and `Environment` resource providers.
  To enable additional resource providers, update `values.yaml` environment variable `OTEL_JAVA_ENABLED_RESOURCE_PROVIDERS` for Java, or set `OTEL_DOTNET_AUTO_{DETECTOR}_RESOURCE_DETECTOR_ENABLED` for .Net.
  For more information see: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/auto-instrumentation-install.md#4-Resource-Attributes

- `chart`: Remove deprecated `image.fluentd.initContainer` configuration option. ([#1995](https://github.com/signalfx/splunk-otel-collector-chart/pull/1995))
  This option was deprecated in version 0.38.0. The same splunk/fluentd-hec image is now used in init containers.

- `chart`: Remove deprecated `extraAttributes.podLabels` configuration option. ([#1994](https://github.com/signalfx/splunk-otel-collector-chart/pull/1994))
  This option was deprecated in version 0.38.0 in favor of `extraAttributes.fromLabels`.
  See migration guide: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0371-to-0380

### 💡 Enhancements 💡

- `clusterReceiver`: Enable k8s.container.status.last_terminated_reason resource attribute for container metrics ([#1968](https://github.com/signalfx/splunk-otel-collector-chart/pull/1968))
- `agent`: Update prometheus receiver configuration for CoreDNS in OpenShift to use secure endpoint and service account token ([#2009](https://github.com/signalfx/splunk-otel-collector-chart/pull/2009))
  - This aligns with OpenShift's default CoreDNS daemonset setup with kube-rbac-proxy which doesn't expose metrics over HTTP.

- `operator`: Bump java to v2.19.0 in helm-charts/splunk-otel-collector/values.yaml ([#1991](https://github.com/signalfx/splunk-otel-collector-chart/pull/1991))
- `Target Allocator`: Update version to `v0.132.0` ([#2019](https://github.com/signalfx/splunk-otel-collector-chart/pull/2019))
  Please review the config `targetAllocator.config.collector_namespace`
  introduced in this version which is set to the release namespace by default.

### 🧰 Bug fixes 🧰

- `agent`: Introducing: `logsCollection.containers.multilineConfigs.maxNumOfLinesToCombine`.
This new field allows to specify max number of lines which will be combined in log entry for multiline log configuration.
In some cases, multiline logs with more than 1000 lines were split into multiple events.
 ([#2012](https://github.com/signalfx/splunk-otel-collector-chart/pull/2012))
- `chart`: Fix per-pod configuration of 'metricsIndex' and 'sourcetype' config for Splunk Platform metrics via annotations ([#1977](https://github.com/signalfx/splunk-otel-collector-chart/pull/1977))

## [0.132.0] - 2025-08-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.132.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.132.0).

### 🛑 Breaking changes 🛑

- `chart`: Remove support of deprecated `distro` and `provider` root-level values.yaml options. ([#1989](https://github.com/signalfx/splunk-otel-collector-chart/pull/1989))
  Use `distribution` instead of `distro` and `cloudProvider` instead of `provider`.
- `chart`: Remove support of deprecated `splunkRealm`, `splunkAccessToken`, `ingestUrl`, `apiUrl`, `metricsEnabled`, `tracesEnabled`, and `logsEnabled` root-level values.yaml options. ([#1985](https://github.com/signalfx/splunk-otel-collector-chart/pull/1985), [#1987](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1987), [#1988](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1988))
  These parameters were deprecated in favor of the structured `splunkObservability` configuration.
  Users must migrate to using:
  - `splunkObservability.realm` instead of `splunkRealm`
  - `splunkObservability.accessToken` instead of `splunkAccessToken`
  - `splunkObservability.ingestUrl` instead of `ingestUrl`
  - `splunkObservability.apiUrl` instead of `apiUrl`
  - `splunkObservability.metricsEnabled` instead of `metricsEnabled`
  - `splunkObservability.tracesEnabled` instead of `tracesEnabled`
  - `splunkObservability.logsEnabled` instead of `logsEnabled`
- `chart`: Remove support of deprecated `otelAgent`, `otelCollector`, and `otelK8sClusterReceiver` configuration sections ([#1990](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1990))
  Use `agent` instead of `otelAgent`, `gateway` instead of `otelCollector`, and `clusterReceiver` instead of `otelK8sClusterReceiver`.
  See migration guide: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0371-to-0380

### 🚩 Deprecations 🚩

- `agent`: Mark `splunkObservability.logsEnabled` as deprecated. ([#1984](https://github.com/signalfx/splunk-otel-collector-chart/pull/1984))
  Logs cannot be sent directly to Splunk Observability anymore.
  Configure `splunkPlatform` to send logs to Splunk Platform and enable Log Observer Connect to view the logs in Splunk Observability.
  See the following documentation for more details: https://help.splunk.com/en/splunk-observability-cloud/manage-data/view-splunk-platform-logs/accomplish-logs-pipeline-rules-in-splunk-platform

### 💡 Enhancements 💡

- `operator`: Drop requirement to install all CRDs except instrumentations. ([#1969](https://github.com/signalfx/splunk-otel-collector-chart/pull/1969))
- `operator`: Upgrade the operator subchart version to 0.92.5 ([#1973](https://github.com/signalfx/splunk-otel-collector-chart/pull/1973))

## [0.131.1] - 2025-08-15

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.131.2](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.131.2).

### 🚩 Deprecations 🚩

- `chart`: Deprecated root-level 'service' config in favor of 'agent.service' and 'gateway.service'. ([#1943](https://github.com/signalfx/splunk-otel-collector-chart/pull/1943))
  - The 'service' config is now deprecated and will be completely removed in a future release. The default `.Values.service` is not set anymore.
  - Please use 'agent.service' and 'gateway.service' for configuring services for the agent and gateway, respectively.
  - When the deprecated 'service' config is present, it completely overrides the component-specific service config for backward compatibility. Make sure to set all fields if passing `.Values.service`.
  - A warning is shown in NOTES.txt if the deprecated config is used.

## [0.131.0] - 2025-08-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.131.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.131.0).

### 🛑 Breaking changes 🛑

- `agent, clusterReceiver`: Changed the default value of the 'useControlPlaneMetricsHistogramData' and 'enableEKSApiServerMetrics' feature gates. These feature gates now default to true and only affect Kubernetes control plane metrics collection. ([#1944](https://github.com/signalfx/splunk-otel-collector-chart/pull/1944))
  - Enabling 'featureGates.useControlPlaneMetricsHistogramData' switches the agent's control plane metrics collection from the legacy `smartagent/*` receivers to `prometheus/*` receivers for k8s control plane components (apiserver, controller-manager, scheduler, etcd, kube-proxy, coredns).
    - This change also enables sending histogram metrics from the above-listed k8s components as OTLP histograms to Splunk Observability.
    - To disable this feature, set `featureGates.useControlPlaneMetricsHistogramData` to false.
  - The 'featureGates.enableEKSApiServerMetrics', now set to true, controls whether EKS API server metrics are collected and sent to Splunk Observability, including OTLP histograms.
    - This change only affects clusterReceiver deployments running in EKS (including vanilla, Fargate, or Auto Mode) clusters.
    - To disable this feature, set `featureGates.enableEKSApiServerMetrics` to false.
  - Please review your configuration if you relied on the previous default of false for these feature gates.

### 💡 Enhancements 💡

- `operator`: Bump java to v2.18.0 in helm-charts/splunk-otel-collector/values.yaml ([#1935](https://github.com/signalfx/splunk-otel-collector-chart/pull/1935))

### 🧰 Bug fixes 🧰

- `agent`: Remove AKS kubeletstat custom CA configuration change. For more information, see the following link https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#aks-kubeletstats-receiver ([#1954](https://github.com/signalfx/splunk-otel-collector-chart/pull/1954))

## [0.130.0] - 2025-07-26

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.130.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.130.0).

### 💡 Enhancements 💡

- `operator`: Bump dotnet to v1.11.0 in helm-charts/splunk-otel-collector/values.yaml ([#1927](https://github.com/signalfx/splunk-otel-collector-chart/pull/1927))
- `operator`: Bump nodejs to v3.3.0 in helm-charts/splunk-otel-collector/values.yaml ([#1926](https://github.com/signalfx/splunk-otel-collector-chart/pull/1926))

### 🧰 Bug fixes 🧰

- `gateway`: Fix typo in deployment-gateway.yaml ([#1939](https://github.com/signalfx/splunk-otel-collector-chart/pull/1939))

## [0.129.0] - 2025-07-15

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.129.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.129.0).

### 🛑 Breaking changes 🛑

- `operator`: Operator instrumentation configuration is now defined under `instrumentation.spec`. This change enables full customization of the instrumentation spec, with all user-provided instrumentation fields merged into the default spec. ([#1873](https://github.com/signalfx/splunk-otel-collector-chart/pull/1873))
  - The configuration structure for operator auto-instrumentation has changed. All settings must now be defined under `instrumentation.spec`.
  - Any configuration directly under `instrumentation.*` (outside of `spec`) will cause an error during helm operations.
  - If you use `.Values.operator.enabled=true` and have overrides for `instrumentation` settings, please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01280-to-01290)

- `agent`: Updates agent config for k8s control plane component's prometheus receivers to filter and keep only a limited set of metrics. ([#1887](https://github.com/signalfx/splunk-otel-collector-chart/pull/1887))
  - This change is only relevant for users who have enabled the useControlPlaneMetricsHistogramData featuregate in their Helm chart configuration.

- `clusterReceiver`: Updates scrape config for EKS apiserver prometheus receiver. The change reflects metrics used in out-of-the-box dashboards in Splunk Observability. ([#1893](https://github.com/signalfx/splunk-otel-collector-chart/pull/1893))
  - This change is only relevant for users who have enabled the `enableEKSApiServerMetrics` featuregate in their Helm chart configuration.


### 💡 Enhancements 💡

- `other`: Add support for EKS Auto Mode (Part 1, hostnetwork). ([#1899](https://github.com/signalfx/splunk-otel-collector-chart/pull/1899))
- `other`: Remove EC2 detector and expand EKS detector which, in addition to IMDS, supports fetching attributes through API (Part 2 - POD Identity) . ([#1903](https://github.com/signalfx/splunk-otel-collector-chart/pull/1903))
  For more information, see the [EKS Auto Mode documentation](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#eks-auto-mode)

- `clusterReceiver`: Enable k8s events in the clusterReceiver by default when exporting logs is enabled. ([#1895](https://github.com/signalfx/splunk-otel-collector-chart/pull/1895))
- `operator`: Bump java to v2.17.1 in helm-charts/splunk-otel-collector/values.yaml ([#1917](https://github.com/signalfx/splunk-otel-collector-chart/pull/1917))
- `opentelemetry-operator-crds`: Bump subchart opentelemetry-operator-crds to 0.0.3. Refer to further [instructions](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/helm-charts/splunk-otel-collector/charts/opentelemetry-operator-crds/README.md#upgrade-notes) for updating CRDs if using  option. ([#1914](https://github.com/signalfx/splunk-otel-collector-chart/pull/1914))
- `operator`: Bump operator to 0.91.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#1914](https://github.com/signalfx/splunk-otel-collector-chart/pull/1914))

### 🧰 Bug fixes 🧰

- `agent`: Fix Signalfx exporter metadata and add necessary mount for bottlerocket OS ([#1898](https://github.com/signalfx/splunk-otel-collector-chart/pull/1898))

## [0.128.0] - 2025-07-08

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.128.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.128.0).

### ❗ Known Issues ❗

- `targetAllocator`: enabling targetAllocator doesn't work in this release due to
  [a bug in the Prometheus library](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/40788)
  which will be fixed in the next release (0.129.0).

### 💡 Enhancements 💡

- `discovery`: Enable service discovery on Windows nodes. ([#1888](https://github.com/signalfx/splunk-otel-collector-chart/pull/1888))
- `gateway, agent`: Add support for OTLP token passthrough in the gateway and agent. ([#1870](https://github.com/signalfx/splunk-otel-collector-chart/pull/1870))
- `gateway`: Add trafficDistribution support to the gateway services. ([#1874](https://github.com/signalfx/splunk-otel-collector-chart/pull/1874))
- `operator`: Bump java to v2.17.0 in helm-charts/splunk-otel-collector/values.yaml ([#1878](https://github.com/signalfx/splunk-otel-collector-chart/pull/1878))

### 🧰 Bug fixes 🧰

- `clusterReceiver`: Remove EKS and EC2 resource detectors for EKS/Fargate distribution as the collectors do not have access to IMDS ([#1891](https://github.com/signalfx/splunk-otel-collector-chart/pull/1891))

## [0.127.0] - 2025-06-18

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.127.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.127.0).

### ❗ Known Issues ❗

- **`simpleprometheusreceiver`: Metrics from this receiver may be missing labels or exhibit unexpected label behavior**
  An issue has been identified in this receiver where labels are not being passed and processed correctly.
  This means Prometheus metrics may be missing expected labels or exhibit unexpected label behavior,
  which can affect internal Collector processing as well as downstream dashboards, alerts, and metric analysis.
  See contrib issue [#40722](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/40722) for more details on this bug.

### 💡 Enhancements 💡

- `clusterReceiver`: Change the cluster receiver internal metrics ports and healthcheck port to be unique, needed to avoid conflicts when running in host network namespace. ([#1859](https://github.com/signalfx/splunk-otel-collector-chart/pull/1859))

### 🧰 Bug fixes 🧰

- `agent`: Fix default config for enabled noDropLogsPipeline feature gate. ([#1866](https://github.com/signalfx/splunk-otel-collector-chart/pull/1866))
- `agent`: Fix scrape target in prometheus receivers added for k8s controlPlaneMetrics. ([#1865](https://github.com/signalfx/splunk-otel-collector-chart/pull/1865))

## [0.126.0] - 2025-06-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.126.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.126.0).

### 💡 Enhancements 💡

- `clusterReceiver`: Adds feature gate `enableEKSApiServerMetrics` to enable prometheus scraping for kubernetes-apiserver metrics from EKS clusters. ([#1831](https://github.com/signalfx/splunk-otel-collector-chart/pull/1831))
- `operator`: Bump java to v2.16.0 in helm-charts/splunk-otel-collector/values.yaml ([#1838](https://github.com/signalfx/splunk-otel-collector-chart/pull/1838))

### 🛑 Breaking changes 🛑

- `agent`/`clusterReceiver`: Upgrade `receiver.prometheusreceiver.RemoveLegacyResourceAttributes` feature gate to `beta` stability (enabled by default) ([#32814](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32814))
  Disable the `receiver.prometheusreceiver.RemoveLegacyResourceAttributes` feature gate to restore previous behavior. This feature gate will be removed in a future release.
  The feature gate is used to remove the following legacy resource attributes:
  `net.host.name` -> `server.address`
  `net.host.port` -> `server.port`
  `http.scheme` -> `url.scheme`
  - If you're using Prometheus receivers with the collector agent or cluster receiver, and have alerts or dashboards based on that data, please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01250-to-01260).

## [0.125.0] - 2025-05-05

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.125.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.125.0).

### 💡 Enhancements 💡

- `agent`: Keep the kubelet CPU usage metrics disabled by default for Splunk Observability users ([#1822](https://github.com/signalfx/splunk-otel-collector-chart/pull/1822))
  `k8s.node.cpu.usage`, `k8s.pod.cpu.usage` and `container.cpu.usage` metrics are enabled by default in the kubeletstats
  receiver upstream, but we disable them for Splunk Observability users because they are not included in the default
  metrics set. If enabled, they will be charged as custom metrics. For now, `container_cpu_utilization` should still be
  used. Later, it will be replaced with one of the CPU metrics from the kubelet receiver once they are fully stabilized
  (e.g., `container.cpu.usage` or `container.cpu.time`).

- `operator`: Bump nodejs to v3.1.2 in helm-charts/splunk-otel-collector/values.yaml ([#1800](https://github.com/signalfx/splunk-otel-collector-chart/pull/1800))

## [0.124.0] - 2025-04-24

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.124.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.124.0).

### 💡 Enhancements 💡

- `operator`: Bump dotnet to v1.10.0 in helm-charts/splunk-otel-collector/values.yaml ([#1700](https://github.com/signalfx/splunk-otel-collector-chart/pull/1700))
- `operator`: Bump java to v2.15.0 in helm-charts/splunk-otel-collector/values.yaml ([#1767](https://github.com/signalfx/splunk-otel-collector-chart/pull/1767))
- `opentelemetry-operator-crds`: Bump subchart opentelemetry-operator-crds to 0.0.2 ([#1786](https://github.com/signalfx/splunk-otel-collector-chart/pull/1786))
- `operator`: Bump operator to 0.86.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1786](https://github.com/signalfx/splunk-otel-collector-chart/pull/1786))

### 🧰 Bug fixes 🧰

- `agent`: Configure AKS KubeletStats receiver on non-windows nodes to use the appropriate CA file. For more information, see the following link https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#aks-kubeletstats-receiver ([#1773](https://github.com/signalfx/splunk-otel-collector-chart/pull/1773))

## [0.122.1] - 2025-04-10

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.122.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.122.0).

### 🛑 Breaking changes 🛑

- `logs`: Disable migrateCheckpoint by default and introduce a new option `migrateLogsCheckpoints` to enable it if needed. ([#1757](https://github.com/signalfx/splunk-otel-collector-chart/pull/1757))
- `agent`: Remove smartagent/signalfx-forwarder from the agent default config. ([#1759](https://github.com/signalfx/splunk-otel-collector-chart/pull/1759))

### 🚩 Deprecations 🚩

- `chart`: Installing certmanager as part of the splunk-otel-collector helm chart is deprecated and will be removed in a future release. ([#1763](https://github.com/signalfx/splunk-otel-collector-chart/pull/1763))

### 💡 Enhancements 💡

- `agent`: Allow featureGates.useControlPlaneMetricsHistogramData to work with any distribution of k8s cluster. ([#1760](https://github.com/signalfx/splunk-otel-collector-chart/pull/1760))
  Users can enable agent.controlPlaneMetrics for k8s components which run on worker nodes
  such as kubedns (gke), coredns (aks, eks) and kube-proxy (eks) with the feature gate
  featureGates.useControlPlaneMetricsHistogramData set to true.
  To disable collection of metrics from specific control plane components, set the corresponding
  component to false in the agent.controlPlaneMetrics configuration. For example:
  agent:
    controlPlaneMetrics:
      coredns:
        enabled: false
      proxy:
        enabled: false

- `all`: Don't hardcode the command in the pod specs ([#1758](https://github.com/signalfx/splunk-otel-collector-chart/pull/1758))
- `all`: Add useMemoryLimitPercentage feature gate ([#1761](https://github.com/signalfx/splunk-otel-collector-chart/pull/1761))

### 🧰 Bug fixes 🧰

- `clusterReceiver`: Removes k8sattributes processor from Splunk Observability events pipeline which is enabled by the chart config `infrastructureMonitoringEventsEnabled`. ([#1746](https://github.com/signalfx/splunk-otel-collector-chart/pull/1746))

## [0.122.0] - 2025-03-31

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.122.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.122.0).

### 🧰 Bug fixes 🧰

- `agent/gateway`: Ensure entity events are sent via gateway if enabled. ([#1732](https://github.com/signalfx/splunk-otel-collector-chart/pull/1732))
- `clusterReceiver`: Removes warning from chart when the clusterReceiver.eventsEnabled flag is set to true. ([#1725](https://github.com/signalfx/splunk-otel-collector-chart/pull/1725))
  The clusterReceiver.eventsEnabled option which used k8s_events receiver is not being deprecated.
  This change removes the warning that was previously displayed when this flag was set to true.

## [0.121.0] - 2025-03-18

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.121.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.121.0).

### 🧰 Bug fixes 🧰

- `other`: Fixed updating metrics' sourcetype with annotations ([#1375](https://github.com/signalfx/splunk-otel-collector-chart/pull/1375))

## [0.120.1] - 2025-03-07

### 💡 Enhancements 💡

- `clusterReceiver`: For the option, `clusterReceiver.eventsEnabled`, the logs pipeline for k8s_events now adds attributes of the type `k8s.<objectkind>.name` and `k8s.<objectkind>.uid`. ([#1691](https://github.com/signalfx/splunk-otel-collector-chart/pull/1691))
  For example, if the log k8s event is about object type `StatefulSet`, the exported log to Splunk will have these 2 additional attributes:
  ```
    k8s.statefulset.name: value(k8s.object.name)
    k8s.statefulset.uid: value(k8s.object.uid)
  ```
  The existing attributes `k8s.object.kind`, `k8s.object.name` and `k8s.object.uid` are still present.
  In addition to these, if the event is for kind Pod, and the k8s.object.fieldPath has a specific container spec, the log will have an additional attribute `k8s.container.name` with the value of the container name.

### 🧰 Bug fixes 🧰

- `agent`: Do not setup the entities pipeline if Splunk Observability isn't enabled. ([#1699](https://github.com/signalfx/splunk-otel-collector-chart/pull/1699))
- `agent`: a fix for a scenario where some logs might be missed due to the pod log file being rolled over during high load, set featureGates.fixMissedLogsDuringLogRotation to true to enable the fix ([#1690](https://github.com/signalfx/splunk-otel-collector-chart/pull/1690))
- `all`: Restore values of `service.name` resource attribute for internal metrics changed in 0.120.0 ([#1692](https://github.com/signalfx/splunk-otel-collector-chart/pull/1692))
  The value of `service.name` resource attribute was changed to `otelcol` due to a library upgrade
  in the Prometheus receiver. This change restores the values that were set before the based on the
  collector mode: `otel-agent`, `otel-collector` or `otel-k8s-cluster-receiver`.

## [0.120.0] - 2025-03-03

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.120.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.120.0).

### 🛑 Breaking changes 🛑

- `operator`: Migrate the operator to use Helm generated TLS certificates instead of cert-manager by default ([#1648](https://github.com/signalfx/splunk-otel-collector-chart/pull/1648))
  - Previously, certificates were generated by cert-manager by default; now they are generated by Helm templates unless configured otherwise.
  - This change simplifies the setup for new users while still supporting those who prefer using cert-manager or other solutions. For more details, see the [related documentation](https://github.com/signalfx/splunk-otel-collector-chart/tree/main/docs/auto-instrumentation-install.md#tls-certificate-requirement-for-kubernetes-operator-webhooks).
  - If you use `.Values.operator.enabled=true` and `.Values.certmanager.enabled=true`, please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01190-to-01200).

### 💡 Enhancements 💡

- `operator`: Bump operator to 0.80.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1678](https://github.com/signalfx/splunk-otel-collector-chart/pull/1678))

## [0.119.0] - 2025-02-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.119.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.119.0).

### 💡 Enhancements 💡

- `chart`: Enable support for custom propagators in `spec.propagators` within Instrumentation Configuration. ([#1663](https://github.com/signalfx/splunk-otel-collector-chart/pull/1663))
  This change allows users to specify custom propagators in `spec.propagators` when configuring OpenTelemetry Instrumentation.

## [0.119.0] - 2025-02-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.119.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.119.0).

### 🚩 Deprecations 🚩

- `clusterReceiver`: Deprecate the `securityContext` field in favor of the `podSecurityContext`. ([#1647](https://github.com/signalfx/splunk-otel-collector-chart/pull/1647))
- `gateway`: Deprecate the `securityContext` field in favor of the `podSecurityContext`. ([#1647](https://github.com/signalfx/splunk-otel-collector-chart/pull/1647))

### 💡 Enhancements 💡

- `clusterReceiver`: Add an option to set the security context for the container. ([#1647](https://github.com/signalfx/splunk-otel-collector-chart/pull/1647))
- `gateway`: Add an option to set the security context for the container. ([#1647](https://github.com/signalfx/splunk-otel-collector-chart/pull/1647))
- `operator`: Bump dotnet to v1.9.0 in helm-charts/splunk-otel-collector/values.yaml ([#1651](https://github.com/signalfx/splunk-otel-collector-chart/pull/1651))
- `operator`: Bump java to v2.13.0 in helm-charts/splunk-otel-collector/values.yaml ([#1669](https://github.com/signalfx/splunk-otel-collector-chart/pull/1669))

## [0.118.0] - 2025-02-04

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.118.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.118.0).

### 💡 Enhancements 💡

- `agent, clusterReceiver, gateway`: Add new dimension `otelcol.service.mode` to internal metrics to identify collector mode ([#1634](https://github.com/signalfx/splunk-otel-collector-chart/pull/1634))
- `operator`: Add tests for Python support ([#1641](https://github.com/signalfx/splunk-otel-collector-chart/pull/1641))
- `chart`: Add optional annotations to secrets ([#1599](https://github.com/signalfx/splunk-otel-collector-chart/pull/1599))
- `operator`: Bump java to v2.12.0 in helm-charts/splunk-otel-collector/values.yaml ([#1631](https://github.com/signalfx/splunk-otel-collector-chart/pull/1631))
- `chart`: Offer to use the UBI image to perform secret validation ([#1635](https://github.com/signalfx/splunk-otel-collector-chart/pull/1635))

## [0.117.0] - 2025-01-22

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.117.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.117.0).

> [!IMPORTANT]
> If upgrading from a version older than 0.116.0, please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0113-to-0116) for details about potential breaking changes.

### 💡 Enhancements 💡

- `operator`: Bump java to v2.11.0 in helm-charts/splunk-otel-collector/values.yaml ([#1608](https://github.com/signalfx/splunk-otel-collector-chart/pull/1608))

## [0.116.0] - 2025-01-17

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.116.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.116.0).

### 🛑 Breaking changes 🛑

- `operator`: Move operator CRD installation to the crds/ folder via a subchart to resolve Helm install ordering issues ([#1561](https://github.com/signalfx/splunk-otel-collector-chart/pull/1561),[#1619](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1619))
  - Users enabling the operator (`.Values.operator.enabled=true`) must now set `operatorcrds.install=true` in Helm values or [manually manage CRD installation](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/auto-instrumentation-install.md#crd-management).
  - Previously, CRDs were installed using templates (`operator.crds.create=true`), which could cause race conditions and installation failures.
  - CRD installation is now handled via Helm's native `crds/` directory for better stability, using a [localized subchart](https://github.com/signalfx/splunk-otel-collector-chart/tree/main/helm-charts/splunk-otel-collector/charts/opentelemetry-operator-crds).
  - If you use `operator.enabled=true` you may have to follow some migration steps, please see the [Upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0113-to-0116).

### 💡 Enhancements 💡

- `collector`: Document the possible use of a FIPS-140 compliant image ([#1582](https://github.com/signalfx/splunk-otel-collector-chart/pull/1582))
- `clusterReceiver`: Configure k8s attributes processor for cluster receiver to ingest events into index defined in namespace annotation ([#1481](https://github.com/signalfx/splunk-otel-collector-chart/pull/1481))
- `agent`: Make it so the default tolerations used to deploy the agent collector account for k8s distribution ([#1562](https://github.com/signalfx/splunk-otel-collector-chart/pull/1562))
  OpenShift infra nodes and AKS system nodes will now be monitored by the agent by default
- `operator`: Bump dotnet to v1.8.0 in helm-charts/splunk-otel-collector/values.yaml ([#1538](https://github.com/signalfx/splunk-otel-collector-chart/pull/1538))
- `operator`: Bump java to v2.10.0 in helm-charts/splunk-otel-collector/values.yaml ([#1551](https://github.com/signalfx/splunk-otel-collector-chart/pull/1551))
- `operator`: Bump nodejs to v2.15.0 in helm-charts/splunk-otel-collector/values.yaml ([#1558](https://github.com/signalfx/splunk-otel-collector-chart/pull/1558))
- `agent, clusterReceiver, gateway`: Update config for scraping internal metrics to use new config interface and loopback address. ([#1573](https://github.com/signalfx/splunk-otel-collector-chart/pull/1573))
  This also drops redundant attributes reported with the internal metrics: `net.host.name` and `server.address`

### 🧰 Bug fixes 🧰

- `agent`: Scrape FS metrics from one host disk mounted to the root to avoid scraping errors since the collector likely doesn't have access to other mounts. ([#1569](https://github.com/signalfx/splunk-otel-collector-chart/pull/1569))
- `gateway`: add signalfx exporter to the gateway traces pipeline to enable APM correlation ([#1607](https://github.com/signalfx/splunk-otel-collector-chart/pull/1607))

## [0.113.0] - 2024-11-22

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.113.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.113.0).

### 🧰 Bug fixes 🧰

- `agent`: Fixes hostmetrics receiver to use the correct mount path of the host's filesystem from inside the container ([#1547](https://github.com/signalfx/splunk-otel-collector-chart/pull/1547))
- `agent`: Exclude scraping filesystem metrics from mounts that are not accessible from inside the container to avoid scraping errors. ([#1550](https://github.com/signalfx/splunk-otel-collector-chart/pull/1550))

## [0.112.1] - 2024-11-20

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.112.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.112.0).

### 🧰 Bug fixes 🧰

- `agent`: Fix bug where hostmetrics receiver was failing to scrape the filesystem ([#1533](https://github.com/signalfx/splunk-otel-collector-chart/pull/1533))
- `operator`: Fix bug where sometimes Instrumentation opentelemetry.io/v1alpha1 can be installed too early ([#1544](https://github.com/signalfx/splunk-otel-collector-chart/pull/1544))

## [0.112.0] - 2024-11-07

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.112.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.112.0).

### 🛑 Breaking changes 🛑

- `agent, gateway, chart`: update default traces exporter to otlphttp ([#1518](https://github.com/signalfx/splunk-otel-collector-chart/pull/1518))
  If you use the sapm exporter with custom settings, you have two options:
  - Migrate your sapm settings to the new otlphttp exporter.
  - Retain SAPM settings by moving them to your agent.config or gateway.config overrides to ensure they remain effective.

### 💡 Enhancements 💡

- `operator`: Bump operator to 0.71.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1511](https://github.com/signalfx/splunk-otel-collector-chart/pull/1511))
- `operator`: Bump java to v2.9.0 in helm-charts/splunk-otel-collector/values.yaml ([#1509](https://github.com/signalfx/splunk-otel-collector-chart/pull/1509))
- `operator`: Bump nodejs to v2.14.0 in helm-charts/splunk-otel-collector/values.yaml ([#1519](https://github.com/signalfx/splunk-otel-collector-chart/pull/1519))

## [0.111.0] - 2024-10-12

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.111.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.111.0).

### 🚩 Deprecations 🚩

- `chart`: Added a note anbout the deprecation of the `fluentd` option in the chart ([#1460](https://github.com/signalfx/splunk-otel-collector-chart/pull/1460))

### 💡 Enhancements 💡

- `chart`: Propagated "sourcetype" to work for metrics and traces ([#1376](https://github.com/signalfx/splunk-otel-collector-chart/pull/1376))
- `agent`: The agent is now deployed with a Kubernetes service for receiving telemetry data by default ([#1485](https://github.com/signalfx/splunk-otel-collector-chart/pull/1485))
- `operator`: Bump dotnet to v1.7.0 in helm-charts/splunk-otel-collector/values.yaml ([#1474](https://github.com/signalfx/splunk-otel-collector-chart/pull/1474))
- `operator`: Bump nodejs to v2.13.0 in helm-charts/splunk-otel-collector/values.yaml ([#1470](https://github.com/signalfx/splunk-otel-collector-chart/pull/1470))

### 🧰 Bug fixes 🧰

- `agent`: Add k8s.node.name attribute to discovered service entities to fix broken link in the UI. ([#1494](https://github.com/signalfx/splunk-otel-collector-chart/pull/1494))

## [0.110.0] - 2024-09-27

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.110.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.110.0).

### 💡 Enhancements 💡

- `template`: Add default metadata key for token to batch processor ([#1467](https://github.com/signalfx/splunk-otel-collector-chart/pull/1467))
  Add default metadata key for token to batch processor.
  This will allow the token to be retrieved from the context. When SAPM is deprecated and
  OTLP used, this will be the normal mode of operation.
- `operator`: Bump operator to 0.56.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#1446](https://github.com/signalfx/splunk-otel-collector-chart/pull/1446))
- `operator`: Bump java to v2.8.1 in helm-charts/splunk-otel-collector/values.yaml ([#1458](https://github.com/signalfx/splunk-otel-collector-chart/pull/1458))

### 🧰 Bug fixes 🧰

- `agent`: use root_path to configure the hostmetricsreceiver, instead of environment variables. ([#1462](https://github.com/signalfx/splunk-otel-collector-chart/pull/1462))

## [0.109.0] - 2024-09-17

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.109.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.109.0).

### 🛑 Breaking changes 🛑

- `operator`: Operator Helm values previously under `.Values.operator.instrumentation.spec.*` have been moved to `.Values.instrumentation.*` ([#1436](https://github.com/signalfx/splunk-otel-collector-chart/pull/1436))
  If you use custom values under `.Values.operator.instrumentation.spec.*` please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01055-01080)

### 💡 Enhancements 💡

- `agent`: Added `fsyncFlag` configuration to allow users to enable fsync on the filestorage. ([#1425](https://github.com/signalfx/splunk-otel-collector-chart/pull/1425))
- `agent`: Add a feature gate `useControlPlaneMetricsHistogramData` ([#1372](https://github.com/signalfx/splunk-otel-collector-chart/pull/1372))
  This feature gate allows to gather control plane metrics and send them as histogram data to Observability Cloud.
  This is an experimental feature under heavy development.

- `agent`: Add base configuration to support the new continuous discovery mechanism. ([#1455](https://github.com/signalfx/splunk-otel-collector-chart/pull/1455))
  The new continuous discovery mechanism is disabled by default. To enable it, set the following values in your configuration:
  ```yaml
  agent:
    discovery:
      enabled: true
    featureGates: splunk.continuousDiscovery
  ```

- `operator`: Bump nodejs to v2.12.0 in helm-charts/splunk-otel-collector/values.yaml ([#1434](https://github.com/signalfx/splunk-otel-collector-chart/pull/1434))

### 🧰 Bug fixes 🧰

- `targetAllocator`: Fix the name of the service account token given when featureGates.explicitMountServiceAccountToken is true ([#1427](https://github.com/signalfx/splunk-otel-collector-chart/pull/1427))

## [0.105.5] - 2024-08-28

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.105.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.105.0).

### 💡 Enhancements 💡

- `all`: Offer an experimental feature gate to mount service tokens in specific containers. ([#1421](https://github.com/signalfx/splunk-otel-collector-chart/pull/1421))
  Kubernetes API access tokens are currently granted via mounting them on all containers of the cluster receiver,
  gateway and daemonset. They are also enabled for the target allocator deployment.
  This experimental change defines how to mount the service account token on specific containers.

## [0.105.4] - 2024-08-26

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.105.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.105.0).

### 🛑 Breaking changes 🛑

- `operator`: Bump java from v1.32.3 to v2.7.0 in helm-charts/splunk-otel-collector/values.yaml ([#1349](https://github.com/signalfx/splunk-otel-collector-chart/pull/1349))
  This is a major upgrade. If you use Java auto-instrumentation please review the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#01053-01070)

### 🧰 Bug fixes 🧰

- `agent`: Retry indefinitely on filelog receiver if noDropLogsPipeline feature gate is enabled. ([#1410](https://github.com/signalfx/splunk-otel-collector-chart/pull/1410))

## [0.105.3] - 2024-08-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.105.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.105.0).

## [0.105.2] - 2024-08-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.105.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.105.0).

### 💡 Enhancements 💡

- `operator`: Bump nodejs to v2.11.0 in helm-charts/splunk-otel-collector/values.yaml ([#1352](https://github.com/signalfx/splunk-otel-collector-chart/pull/1352))

## [0.105.1] - 2024-08-20

### 🛑 Breaking changes 🛑

- `agent`: Remove the deprecated OTLP HTTP port 55681 ([#1359](https://github.com/signalfx/splunk-otel-collector-chart/pull/1359))

### 🚀 New components 🚀

- `targetAllocator`: Add support for Target Allocator as part of the Helm chart. ([#689](https://github.com/signalfx/splunk-otel-collector-chart/pull/689))
  Target Allocator is a component of the OpenTelemetry Operator.
  With this addition, the target allocator is deployed to work in coordination with the daemonset of collectors.
  It applies a default configuration applying scrape targets per node.
  By default, the Target Allocator looks for all ServiceMonitor and PodMonitor CRDs across all namespaces.
  This can be tuned by overriding the service account associated with the Target Allocator.


### 💡 Enhancements 💡

- `agent`: Add an experimental feature gate to use exporter batching instead of the batch processor ([#1387](https://github.com/signalfx/splunk-otel-collector-chart/pull/1387))
- `all`: Set automountServiceAccountToken to true explicitly for the chart's defined service accounts. ([#1390](https://github.com/signalfx/splunk-otel-collector-chart/pull/1390))
- `operator`: Bump java to v1.32.3 in helm-charts/splunk-otel-collector/values.yaml ([#1355](https://github.com/signalfx/splunk-otel-collector-chart/pull/1355))

### 🧰 Bug fixes 🧰

- `agent`: Remove apparmor pod annotation by enabled default ([#1378](https://github.com/signalfx/splunk-otel-collector-chart/pull/1378))

## [0.105.0] - 2024-07-30

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.105.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.105.0).

## [0.104.0] - 2024-07-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.104.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.104.0).

### 💡 Enhancements 💡

- `operator`: Bump nodejs to v2.9.0 in helm-charts/splunk-otel-collector/values.yaml ([#1337](https://github.com/signalfx/splunk-otel-collector-chart/pull/1337))

## [0.103.0] - 2024-06-27

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.103.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.103.0).

### 💡 Enhancements 💡

- `operator`: Bump dotnet to v1.6.0 in helm-charts/splunk-otel-collector/values.yaml ([#1327](https://github.com/signalfx/splunk-otel-collector-chart/pull/1327))
- `operator`: Bump java to v1.32.2 in helm-charts/splunk-otel-collector/values.yaml ([#1328](https://github.com/signalfx/splunk-otel-collector-chart/pull/1328))

### 🧰 Bug fixes 🧰

- `chart`: Updated Security Context Constraints for OpenShift support to fix formatting issues and add support for the operator service account ([#1325](https://github.com/signalfx/splunk-otel-collector-chart/pull/1325))

## [0.102.0] - 2024-06-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.102.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.102.1).

### 💡 Enhancements 💡

- `agent`: Add a pod annotation that designates the otel-collector as unconfined for appArmor-protected environments ([#1313](https://github.com/signalfx/splunk-otel-collector-chart/pull/1313))

## [0.101.0] - 2024-05-29

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.101.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.101.0).

### 💡 Enhancements 💡

- `operator`: Bump java to v1.32.1 in helm-charts/splunk-otel-collector/values.yaml ([#1300](https://github.com/signalfx/splunk-otel-collector-chart/pull/1300))

### 🧰 Bug fixes 🧰

- `operator`: Fix issue where SPLUNK_OTEL_AGENT env var was set before custom operator.instrumentation.spec.env env vars ([#1292](https://github.com/signalfx/splunk-otel-collector-chart/pull/1292))

## [0.100.0] - 2024-05-09

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.100.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.100.0).

## [0.99.1] - 2024-05-09

### 💡 Enhancements 💡

- `agent`: Add an option `skipInitContainers` to skip init container setting file ACLs when the `runAsUser` and
  `runAsGroup` are provided. This is useful when the user wants to manage the file ACLs themselves.
  ([#1286](https://github.com/signalfx/splunk-otel-collector-chart/pull/1286))
- `operator`: Bump dotnet to v1.5.0 in helm-charts/splunk-otel-collector/values.yaml ([#1282](https://github.com/signalfx/splunk-otel-collector-chart/pull/1282))

## [0.99.0] - 2024-04-26

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.99.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.99.0).

### 💡 Enhancements 💡

- `operator`: Bump java to v1.32.0 in helm-charts/splunk-otel-collector/values.yaml ([#1231](https://github.com/signalfx/splunk-otel-collector-chart/pull/1231),[#1265](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1265))
- `operator`: Bump nodejs to v2.8.0 in helm-charts/splunk-otel-collector/values.yaml ([#1269](https://github.com/signalfx/splunk-otel-collector-chart/pull/1269))

## [0.98.0] - 2024-04-16

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.98.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.98.0).

### 💡 Enhancements 💡

- `agent`: Enable `retry_on_failure` for journald receiver ([#764](https://github.com/signalfx/splunk-otel-collector-chart/pull/764))
  In case of temporary errors the journald receiver should slow down and retry the log delivery instead of dropping it.

### 🧰 Bug fixes 🧰

- `clusterReceiver`: Added clusterRole for events.k8s.io, without it k8sobjectsreceiver throws an error on startup ([#1238](https://github.com/signalfx/splunk-otel-collector-chart/pull/1238))

## [0.97.0] - 2024-03-28

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.97.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.97.0).

### 💡 Enhancements 💡

- `chart`: Removed memory_ballast property from all the configs ([#1240](https://github.com/signalfx/splunk-otel-collector-chart/pull/1240))
- `operator`: Bump operator to 0.49.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#1221](https://github.com/signalfx/splunk-otel-collector-chart/pull/1221))

## [0.96.0] - 2024-03-12

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.96.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.96.1).

### 💡 Enhancements 💡

- `operator`: Bump certmanager to v1.14.4 in helm-charts/splunk-otel-collector/Chart.yaml ([#1205](https://github.com/signalfx/splunk-otel-collector-chart/pull/1205))
- `operator`: Bump java to v1.31.0 in helm-charts/splunk-otel-collector/values.yaml ([#1199](https://github.com/signalfx/splunk-otel-collector-chart/pull/1199))

## [0.95.0] - 2024-03-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.95.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.95.0).

### 💡 Enhancements 💡

- `chart`: The request is to add the namespace to the generated templates, for commands like "helm template --namespace mynamespace (...)" ([#1011](https://github.com/signalfx/splunk-otel-collector-chart/pull/1011))

## [0.94.0] - 2024-03-01

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.94.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.94.0).

### 💡 Enhancements 💡

- `operator`: Bump certmanager to v1.14.3 in helm-charts/splunk-otel-collector/Chart.yaml ([#1182](https://github.com/signalfx/splunk-otel-collector-chart/pull/1182))
- `operator`: Bump java to v1.30.3 in helm-charts/splunk-otel-collector/values.yaml ([#1188](https://github.com/signalfx/splunk-otel-collector-chart/pull/1188))
- `operator`: Bump nodejs to v2.7.1 in helm-charts/splunk-otel-collector/values.yaml ([#1180](https://github.com/signalfx/splunk-otel-collector-chart/pull/1180))

### 🧰 Bug fixes 🧰

- `clusterReceiver`: Bring back the default translations for kubelet metrics in EKS Fargate ([#1174](https://github.com/signalfx/splunk-otel-collector-chart/pull/1174))
- `agent`: Remove a post-delete hook which targeted one a single node for reverting file ACLs. ([#1175](https://github.com/signalfx/splunk-otel-collector-chart/pull/1175))
  The removed hook was intended to undo the ACLs set on log directories when
  runAsUser and runAsGroup are provided. An initContainer run as root-user updates
  the permissions of log directories to allow read access to the provided uid/gid.
  But there is no graceful way to revert these ACLs on each node as part of the
  chart uninstallation process.


## [0.93.3] - 2024-02-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.93.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.93.0).

### 🛑 Breaking changes 🛑

- `networkExplorer`: The `networkExplorer` option was deprecated in 0.88.0. It is now entirely removed. ([#1156](https://github.com/signalfx/splunk-otel-collector-chart/pull/1156))

### 🧰 Bug fixes 🧰

- `agent`: Fix GKE Autopilot deployment ([#1171](https://github.com/signalfx/splunk-otel-collector-chart/pull/1171))

## [0.93.2] - 2024-02-15

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.93.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.93.0).

### 💡 Enhancements 💡

- `operator`:  Improve Auto-instrumentation Configurations ([#1166](https://github.com/signalfx/splunk-otel-collector-chart/pull/1166))

## [0.93.1] - 2024-02-14

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.93.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.93.0).

### 💡 Enhancements 💡

- `agent`: Change the default sending queue size from 5000 to 1000. ([#1157](https://github.com/signalfx/splunk-otel-collector-chart/pull/1157))
- `operator`: Bump dotnet to v1.4.0 in helm-charts/splunk-otel-collector/values.yaml ([#1158](https://github.com/signalfx/splunk-otel-collector-chart/pull/1158))
- `operator`: Bump certmanager to v1.14.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1152](https://github.com/signalfx/splunk-otel-collector-chart/pull/1152))
  - ⚠️ Known Issue fixed in certmanager v1.14.2
    - In cert-manager [v1.14.1](https://github.com/cert-manager/cert-manager/releases/tag/v1.14.1), the CA and SelfSigned issuers issue certificates with SANs set to non-critical even when the subject is empty. It incorrectly copies the critical field from the CSR.
    - To avoid this issue, please upgrade directly to version 0.93.1 of this chart when utilizing `certmanager.enabled=true`, thereby bypassing affected versions v0.92.1 and v0.93.0.

### 🧰 Bug fixes 🧰

- `chart`: Remove networkExplorer deprecation note that can cause the chart installation to fail ([#1162](https://github.com/signalfx/splunk-otel-collector-chart/pull/1162))

## [0.93.0] - 2024-02-08

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.93.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.93.0).

### 🛑 Breaking changes 🛑

- `internal metrics`: Stop reporting metrics sent by the batch processor ([#1147](https://github.com/signalfx/splunk-otel-collector-chart/pull/1147))

### 💡 Enhancements 💡

- `operator`: Bump java to v1.30.1 in helm-charts/splunk-otel-collector/values.yaml ([#1139](https://github.com/signalfx/splunk-otel-collector-chart/pull/1139))
- `operator`: Bump nodejs to v2.7.0 in helm-charts/splunk-otel-collector/values.yaml ([#1143](https://github.com/signalfx/splunk-otel-collector-chart/pull/1143))

## [0.92.1] - 2024-02-06

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.92.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.92.0).

### 💡 Enhancements 💡

- `operator`: Bump certmanager to v1.14.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#1140](https://github.com/signalfx/splunk-otel-collector-chart/pull/1140))

### 🧰 Bug fixes 🧰

- `chart`: Fix Helm chart incorrectly handling Kubernetes versions containing a "+" character, causing deployment errors for PodDisruptionBudget in certain environments ([#1144](https://github.com/signalfx/splunk-otel-collector-chart/pull/1144))
- `collector`: Fix template function to be able to convert non-integer memory limit values ([#1128](https://github.com/signalfx/splunk-otel-collector-chart/pull/1128))
- `operator`: Fix issue where the collector agent exporter endpoint used in operator .NET and Python auto-instrumentation was missing the proper IP address ([#1129](https://github.com/signalfx/splunk-otel-collector-chart/pull/1129))

## [0.92.0] - 2024-01-23

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.92.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.92.0).

### 💡 Enhancements 💡

- `operator`: Use the Splunk Distribution of OpenTelemetry .NET docker image by default when auto-instrumenting with the operator ([#1098](https://github.com/signalfx/splunk-otel-collector-chart/pull/1098))
- `other`: Added support for rerouting metrics index with pod/namespace annotations ([#1053](https://github.com/signalfx/splunk-otel-collector-chart/pull/1053))
- `chart`: Allows to set the hostNetwork parameter in chart ([#1014](https://github.com/signalfx/splunk-otel-collector-chart/pull/1014))
- `operator`: Bump dotnet to v1.3.0 in helm-charts/splunk-otel-collector/values.yaml ([#1121](https://github.com/signalfx/splunk-otel-collector-chart/pull/1121))
- `operator`: Bump operator to 0.46.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#1116](https://github.com/signalfx/splunk-otel-collector-chart/pull/1116),[#1124](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1124))

## [0.91.1] - 2024-01-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.91.3](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.91.3).

### 💡 Enhancements 💡

- `agent`: linux: Adopt discovery mode in agent and provide agent.discovery.properties value mapping ([#1108](https://github.com/signalfx/splunk-otel-collector-chart/pull/1108))
- `chart`: Make clusterName optional in EKS and GKE ([#1056](https://github.com/signalfx/splunk-otel-collector-chart/pull/1056),[#1067](https://github.com/signalfx/splunk-otel-collector-chart/pull/#1067))
- `operator`: Bump certmanager to v1.13.3 in helm-charts/splunk-otel-collector/Chart.yaml ([#1085](https://github.com/signalfx/splunk-otel-collector-chart/pull/1085))
- `operator`: Bump nodejs to v2.6.1 in helm-charts/splunk-otel-collector/values.yaml ([#1094](https://github.com/signalfx/splunk-otel-collector-chart/pull/1094))
- `operator`: Bump operator to 0.44.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1084](https://github.com/signalfx/splunk-otel-collector-chart/pull/1084))

### 🧰 Bug fixes 🧰

- `agent`: Change the default directory of the journald receiver ([#1110](https://github.com/signalfx/splunk-otel-collector-chart/pull/1110))

## [0.91.0] - 2023-12-12

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.91.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.91.0).

### 🛑 Breaking changes 🛑

- `networkExplorer`: Remove networkExplorer from helm chart ([#1076](https://github.com/signalfx/splunk-otel-collector-chart/pull/1076))
  Network explorer is no longer part of this helm chart and should be installed separately.
  See https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/advanced-configuration.md#using-opentelemetry-ebpf-helm-chart-with-splunk-opentelemetry-collector-for-kubernetes
  for more details.

### 💡 Enhancements 💡

- `operator`: Bump nodejs to v2.6.0 in helm-charts/splunk-otel-collector/values.yaml ([#1080](https://github.com/signalfx/splunk-otel-collector-chart/pull/1080))

## [0.90.1] - 2023-12-08

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.90.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.90.0).

### 🧰 Bug fixes 🧰

- `agent`: Fix GKE Autopilot deployment ([#1071](https://github.com/signalfx/splunk-otel-collector-chart/pull/1071))

## [0.90.0] - 2023-12-07

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.90.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.90.0).

### 💡 Enhancements 💡

- `operator`: Bump java to v1.30.0 in helm-charts/splunk-otel-collector/values.yaml ([#1064](https://github.com/signalfx/splunk-otel-collector-chart/pull/1064))
- `operator`: Bump version of the operator subchart to 0.43.0 ([#1049](https://github.com/signalfx/splunk-otel-collector-chart/pull/1049))

## [0.88.0] - 2023-11-22

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.88.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.88.0).

### 🚩 Deprecations 🚩

- `networkExplorer`: Deprecate networkExplorer in favor of the upstream OpenTelemetry eBPF helm chart. ([#1026](https://github.com/signalfx/splunk-otel-collector-chart/pull/1026))

### 💡 Enhancements 💡

- `agent`: Remove the use of the `max_connections` configuration key, use `max_idle_conns_per_host` instead. ([#1034](https://github.com/signalfx/splunk-otel-collector-chart/pull/1034))
- `operator`: Bump java to v1.29.1 in helm-charts/splunk-otel-collector/values.yaml ([#1042](https://github.com/signalfx/splunk-otel-collector-chart/pull/1042))
- `operator`: Bump nodejs to v2.5.1 in helm-charts/splunk-otel-collector/values.yaml ([#1040](https://github.com/signalfx/splunk-otel-collector-chart/pull/1040))
- `operator`: Bump operator to 0.42.3 in helm-charts/splunk-otel-collector/Chart.yaml ([#1025](https://github.com/signalfx/splunk-otel-collector-chart/pull/1025))

## [0.87.0] - 2023-11-15

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.87.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.87.0).

### 💡 Enhancements 💡

- `agent, fluentd`: Allow users to override `enable_stat_watcher` and `refresh_interval` for tail plugin from values.yaml ([#982](https://github.com/signalfx/splunk-otel-collector-chart/pull/982))
- `agent`: Add combineWith field to multiline configuration ([#756](https://github.com/signalfx/splunk-otel-collector-chart/pull/756))
- `operator`: Bump certmanager to v1.13.2 in helm-charts/splunk-otel-collector/Chart.yaml ([#1007](https://github.com/signalfx/splunk-otel-collector-chart/pull/1007))
- `operator`: Bump operator to 0.41.0 in helm-charts/splunk-otel-collector/Chart.yaml ([#985](https://github.com/signalfx/splunk-otel-collector-chart/pull/985))

### 🧰 Bug fixes 🧰

- `chart`: Remove by default empty allowedFlexVolumes ([#981](https://github.com/signalfx/splunk-otel-collector-chart/pull/981))
  Removed the allowedFlexVolumes empty field since it does not provide any default additional benefits for the users.

## [0.86.1] - 2023-10-13

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.86.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.86.0).

### 💡 Enhancements 💡

- `operator`: use splunk-otel-js as Docker image for node.js auto-instrumentation ([#967](https://github.com/signalfx/splunk-otel-collector-chart/pull/967))

## [0.86.0] - 2023-10-11

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.86.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.86.0).

### 💡 Enhancements 💡

- `agent`: Drop time attribute used during parsing the time from log record, so it is not reported as an extra field. ([#912](https://github.com/signalfx/splunk-otel-collector-chart/pull/912))
- `agent`: Change the default logs collection engine (`logsEngine`) to the native OpenTelemetry logs collection (`otel`) ([#934](https://github.com/signalfx/splunk-otel-collector-chart/pull/934))
  If you want to keep using Fluentd sidecar for the logs collection, set `logsEngine' to 'fluentd` in your values.yaml
- `operator`: Bump certmanager to v1.13.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#941](https://github.com/signalfx/splunk-otel-collector-chart/pull/941))
- `operator`: Bump operator to 0.39.1 in helm-charts/splunk-otel-collector/Chart.yaml ([#940](https://github.com/signalfx/splunk-otel-collector-chart/pull/940))
- `chart`: Add support for OpenTelemetry CHANGELOG.md generator tool, see [chloggen](https://github.com/open-telemetry/opentelemetry-operator/tree/main/.chloggen) ([#923](https://github.com/signalfx/splunk-otel-collector-chart/pull/923))

### 🧰 Bug fixes 🧰

- `networkExplorer`: delete deprecated Pod Security Policy from networkExplorer templates ([#896](https://github.com/signalfx/splunk-otel-collector-chart/pull/896))
- `operator`: Fix Operator helm template issues ([#938](https://github.com/signalfx/splunk-otel-collector-chart/pull/938))
  Resolves smaller issues in the Helm template related to the of non-default Operator auto-instrumentation values, which could trigger deployment failures

## [0.85.0] - 2023-09-19

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.85.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.85.0).

### 🚀 New components 🚀

- Add `component` label to daemonset pods and optional k8s service for agent daemonset which can be enabled with `agent.service.enabled` config. [#740](https://github.com/signalfx/splunk-otel-collector-chart/pull/740)

### 💡 Enhancements 💡

- Update Splunk Fluend HEC docker image to v1.3.3 [#924](https://github.com/signalfx/splunk-otel-collector-chart/pull/924)
- Add ability to update and track operator auto-instrumentation images [#917](https://github.com/signalfx/splunk-otel-collector-chart/pull/917)
  - [BREAKING CHANGE] Refactored auto-instrumentation image definition from operator.instrumentation.spec.{library}.image
    to operator.instrumentation.spec.{library}.repository and operator.instrumentation.spec.{library}.tag.
    See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0840-0850)
- Upgrade the Splunk OpenTelemetry Collector for Kubernetes dependencies [#32](https://github.com/signalfx/splunk-otel-collector-chart/pull/932),[#929](https://github.com/signalfx/splunk-otel-collector-chart/pull/929)
  - opentelemetry-operator upgraded to [v0.37.1](https://github.com/open-telemetry/opentelemetry-helm-charts/releases/tag/opentelemetry-operator-0.37.1)
  - Java auto-instrumentation upgraded from 1.28.0 to [1.28.0](https://github.com/signalfx/splunk-otel-java/releases/tag/v1.28.0)

## [0.84.0] - 2023-09-11

### 💡 Enhancements 💡

- Disable `opencensus.resourcetype` resource attribute in k8s_cluster receiver [#914](https://github.com/signalfx/splunk-otel-collector-chart/pull/914)
  - This change does not affect Splunk Observability users since it has already been disabled in the default translation rules of the Signalfx exporter
- Disable signalfx exporter default translations in clusterReceiver deployment [#915](https://github.com/signalfx/splunk-otel-collector-chart/pull/915)
  - This change improves performance of clusterReceiver, but can be breaking if the deprecated signalfx exporter `translation_rules` option is being used
- Upgrade the Splunk OpenTelemetry Collector for Kubernetes dependencies [#919](https://github.com/signalfx/splunk-otel-collector-chart/pull/919),[#909](https://github.com/signalfx/splunk-otel-collector-chart/pull/909)
- opentelemetry-operator upgraded to [v0.37.0](https://github.com/open-telemetry/opentelemetry-helm-charts/releases/tag/opentelemetry-operator-0.37.0)
- cert-manager upgraded to [v1.12.4](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.4)

### 🧰 Bug fixes 🧰

- Enable native OTel logs collection (logsEngine=otel) in GKE Autopilot [#809](https://github.com/signalfx/splunk-otel-collector-chart/pull/809)

### 🚀 New components 🚀

- Configuration of persistent buffering for agent [861](https://github.com/signalfx/splunk-otel-collector-chart/pull/861)
- Add option to disable Openshift SecurityContextConstraint resource [#843](https://github.com/signalfx/splunk-otel-collector-chart/pull/843)

## [0.83.0] - 2023-08-18

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.83.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.83.0).

### 💡 Enhancements 💡

- Upgrade the Splunk OpenTelemetry Collector for Kubernetes dependencies [#885](https://github.com/signalfx/splunk-otel-collector-chart/pull/885),[#876](https://github.com/signalfx/splunk-otel-collector-chart/pull/876)
  - opentelemetry-operator upgraded to [v0.35.0](https://github.com/open-telemetry/opentelemetry-helm-charts/releases/tag/opentelemetry-operator-0.35.0)
  - cert-manager upgraded to [v1.12.3](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.3)

### 🧰 Bug fixes 🧰

- Fix for secret name which now respects the same overrides as other resources in the chart [#873](https://github.com/signalfx/splunk-otel-collector-chart/pull/873)
- Update the secret validation hook pod to use imagePullSecrets instead of possible non-existing serviceAccountName [#888](https://github.com/signalfx/splunk-otel-collector-chart/pull/888)

## [0.82.0] - 2023-08-02

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.82.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.82.0).

### 🧰 Bug fixes 🧰

- Use "ContainerAdministrator" user for windows nodes by default [#809](https://github.com/signalfx/splunk-otel-collector-chart/pull/809)

## [0.81.0] - 2023-07-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.81.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.81.0).

### 💡 Enhancements 💡

- Upgrade the Splunk OpenTelemetry Collector for Kubernetes dependencies [#856](https://github.com/signalfx/splunk-otel-collector-chart/pull/856),[#858](https://github.com/signalfx/splunk-otel-collector-chart/pull/858)
  - opentelemetry-operator upgraded from 0.32.0 to [0.34.0](https://github.com/open-telemetry/opentelemetry-helm-charts/releases/tag/opentelemetry-operator-0.34.0)
  - Java auto-instrumentation upgraded from 1.24.0 to [1.26.0](https://github.com/signalfx/splunk-otel-java/releases/tag/v1.26.0)

### 🧰 Bug fixes 🧰

- Set cluster_name for host logs too if renameFieldsSck is enabled [#837](https://github.com/signalfx/splunk-otel-collector-chart/pull/837)
- Fix `smartagent` collectd based monitors on read-only filesystems [#839](https://github.com/signalfx/splunk-otel-collector-chart/pull/839)

### 🚀 New components 🚀

- Update PodDisruptionBudgets API version to allow both `policy/v1beta1` and `policy/v1` [#835](https://github.com/signalfx/splunk-otel-collector-chart/pull/835)
- Update clusterrole to allow collector to check for the `aws-auth` configmap in EKS clusters [#840](https://github.com/signalfx/splunk-otel-collector-chart/pull/840)
- Add support to create default Instrumentation for operator based auto-instrumentation [#836](https://github.com/signalfx/splunk-otel-collector-chart/pull/836)

## [0.80.0] - 2023-06-27

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.80.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.80.0).

### 💡 Enhancements 💡

- Add `service.name` resource attribute to logs if `autodetect.istio` is enabled using transform processor. This change
  removes the limitation of `service.name` attribute being available only with logsEngine=fluentd.
  [#823](https://github.com/signalfx/splunk-otel-collector-chart/pull/823)
- Upgrade the Splunk OpenTelemetry Collector for Kubernetes dependencies [#828](https://github.com/signalfx/splunk-otel-collector-chart/pull/828)
  - cert-manager upgraded from 1.11.1 to [1.12.2](https://github.com/cert-manager/cert-manager/releases/tag/v1.12.2)
  - opentelemetry-operator upgraded from 0.28.0 to [0.32.0](https://github.com/open-telemetry/opentelemetry-helm-charts/releases/tag/opentelemetry-operator-0.32.0)
- Update the log level for metric scrape failures of the smartagent/kubernetes-proxy receiver from error to debug when distribution='' [#832](https://github.com/signalfx/splunk-otel-collector-chart/pull/832)

## [0.79.1] - 2023-06-22

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.79.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.79.1).

### 🧰 Bug fixes 🧰

- Fix cri-o log format time layout [#817](https://github.com/signalfx/splunk-otel-collector-chart/pull/817)
- Align the set of default resource attributes added by k8s attributes processor if the gateway is enabled [#820](https://github.com/signalfx/splunk-otel-collector-chart/pull/820)

## [0.79.0] - 2023-06-16

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.79.0](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.79.0).

### 🚀 New components 🚀

- Adopt new control-plane node toleration [#814](https://github.com/signalfx/splunk-otel-collector-chart/pull/814)

### 💡 Enhancements 💡

- Update the Kubernetes Proxy monitor for OpenShift clusters to start using secure ports 9101 or 29101 with authentication [#810](https://github.com/signalfx/splunk-otel-collector-chart/pull/810)

## [0.78.0] - 2023-06-07

This Splunk OpenTelemetry Collector for Kubernetes release adopts the [Splunk OpenTelemetry Collector v0.78.1](https://github.com/signalfx/splunk-otel-collector/releases/tag/v0.78.1).

### 🚀 New components 🚀

- Adopt Openshift distribution in Network Explorer [#804](https://github.com/signalfx/splunk-otel-collector-chart/pull/804)

## [0.77.0] - 2023-06-05

### 🚀 New components 🚀

- Add `serviceAccountName` to secret validation hook pod [#781](https://github.com/signalfx/splunk-otel-collector-chart/pull/781)
- Allow enabling profiling only for Observability [#788](https://github.com/signalfx/splunk-otel-collector-chart/pull/788)
- Add storage to filelog receiver for extraFileLog [#755](https://github.com/signalfx/splunk-otel-collector-chart/pull/755)
- Add Openshift support for Network-Explorer [804](https://github.com/signalfx/splunk-otel-collector-chart/pull/804)

### 💡 Enhancements 💡

- Avoid `runAsUser` in SecurityContext for Windows [#797](https://github.com/signalfx/splunk-otel-collector-chart/pull/797)

## [0.76.0] - 2023-05-04

### 🚀 New components 🚀

- Option to use lightprometheus receiver through a feature gate for metrics collection from discovered Prometheus endpoints [757](https://github.com/signalfx/splunk-otel-collector-chart/pull/757)

### 💡 Enhancements 💡

- Add `logsCollection.containers.maxRecombineLogSize` config option with default 1Mb value which is applied
  to `max_log_size` option of the multiline recombine operators
- Move `extraOperators` above `multilineConfig` in _otel_agent.tpl, as `extraOperators` gets
  skipped when we use both `multilineConfig` AND `extraOperators` in values.yaml
- Enable retry mechanism in filelog receiver to avoid dropping logs on backpressure from the downstream
  pipeline components [#764](https://github.com/signalfx/splunk-otel-collector-chart/pull/764)
- Drop excessive istio attributes to avoid running into the dimensions limit when scraping istio metrics is enabled [765](https://github.com/signalfx/splunk-otel-collector-chart/pull/765)

### 🧰 Bug fixes 🧰

- Fix k8s.cluster.name resource attribute for logs in GCP [#771](https://github.com/signalfx/splunk-otel-collector-chart/pull/771)

## [0.75.0] - 2023-04-17

### 💡 Enhancements 💡

- Update the Kubernetes scheduler monitor to stop using insecure port 10251 and start using secure port 10259 with authentication [#711](https://github.com/signalfx/splunk-otel-collector-chart/pull/711)
- Upgrade splunk-otel-collector image to 0.75.0

### 🧰 Bug fixes 🧰

- Sending request timeouts in k8s cluster receiver deployment on big k8s clusters [#717](https://github.com/signalfx/splunk-otel-collector-chart/pull/717)
- Properly handle enableMetrics in Network Explorer Reducer template [#724](https://github.com/signalfx/splunk-otel-collector-chart/pull/724)

### 🚀 New components 🚀

- Add support for Operator based Java auto-instrumentation [#701](https://github.com/signalfx/splunk-otel-collector-chart/pull/701)
- Add experimental support for deploying OpenTelemetry Operator as a subchart [#691](https://github.com/signalfx/splunk-otel-collector-chart/pull/691)
- Improve documentation about providing tokens as Kubernetes secrets [#707](https://github.com/signalfx/splunk-otel-collector-chart/pull/691)
- Expose `idle_conn_timeout` on the splunk HEC exporters [#728](https://github.com/signalfx/splunk-otel-collector-chart/pull/728)
- Add `logsCollection.containers.maxRecombineLogSize` config option with default 1Mb value which is applied
  to `max_log_size` option of the default recombine operators [#713](https://github.com/signalfx/splunk-otel-collector-chart/pull/713)

## [0.72.0] - 2023-03-09

### 🚀 New components 🚀

- Add functional test coverage for Network Explorer metrics [#684](https://github.com/signalfx/splunk-otel-collector-chart/pull/684)
- Apply the same resources to init containers as allocated to the otel agent container [#690](https://github.com/signalfx/splunk-otel-collector-chart/pull/690)

## [0.71.0] - 2023-03-01

### 🚀 New components 🚀

- Added examples for supported Kubernetes distributions and Kubernetes clusters with windows nodes ([#663](https://github.com/signalfx/splunk-otel-collector-chart/pull/663))
- Refactored the examples and rendered directories into one for better usability ([#658](https://github.com/signalfx/splunk-otel-collector-chart/pull/658))

### 💡 Enhancements 💡

- Docker metadata turned off by default ([#655](https://github.com/signalfx/splunk-otel-collector-chart/pull/665))

### 🧰 Bug fixes 🧰

- Translation of `k8s.pod.labels.app` attribute to SCK format ([#660](https://github.com/signalfx/splunk-otel-collector-chart/pull/660))

## [0.70.0] - 2023-01-31

### 🚀 New components 🚀

- Support sending traces via Splunk HEC exporter ([#629](https://github.com/signalfx/splunk-otel-collector-chart/pull/629) - thanks to @mr-miles)

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.70.0, skipping 0.69.0 release ([#653](https://github.com/signalfx/splunk-otel-collector-chart/pull/653))

### 🧰 Bug fixes 🧰

- Fix invalid OpenShift SecurityContextConstraints template ([#652](https://github.com/signalfx/splunk-otel-collector-chart/pull/652))
- Limit `clusterReceiver.eventsEnabled` deprecation warning to feature users ([#648](https://github.com/signalfx/splunk-otel-collector-chart/pull/648))
- Fix noop validation for missing platform info ([#649](https://github.com/signalfx/splunk-otel-collector-chart/pull/649))

## [0.68.0] - 2023-01-25

### 🚀 New components 🚀

- Allow to overwrite default SecurityContextConstraints rules with values.yaml file ([#643](https://github.com/signalfx/splunk-otel-collector-chart/pull/643))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.68.1 ([#640](https://github.com/signalfx/splunk-otel-collector-chart/pull/640))

### 🧰 Bug fixes 🧰

- Default recombine operator for the docker container engine ([#627](https://github.com/signalfx/splunk-otel-collector-chart/pull/627))
- Added acl to journald log directory ([#639](https://github.com/signalfx/splunk-otel-collector-chart/pull/639))

## [0.67.0] - 2022-12-19

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.67.0 ([#612](https://github.com/signalfx/splunk-otel-collector-chart/pull/612))

### 🧰 Bug fixes 🧰

- Make sure the daemonset can start in GKE Autopiot ([#608](https://github.com/signalfx/splunk-otel-collector-chart/pull/608))
- Make containerd engine default in for fluentd logs and use always use it in GKE Autopiot ([#609](https://github.com/signalfx/splunk-otel-collector-chart/pull/609))
- Temporary disable compression in Splunk Observability logs exporter until
  0.68.0 to workaround a compression bug ([#610](https://github.com/signalfx/splunk-otel-collector-chart/pull/610))

## [0.66.1] - 2022-12-08

### 🧰 Bug fixes 🧰

- Fixed network explorer image pull secrets

## [0.66.0] - 2022-12-06

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.66.0 ([#593](https://github.com/signalfx/splunk-otel-collector-chart/pull/593))

## [0.64.0] - 2022-11-22

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.64.0 ([#589](https://github.com/signalfx/splunk-otel-collector-chart/pull/589))

### 🧰 Bug fixes 🧰

## [0.62.2] - 2022-11-21

- Added Network Explorer components

## [0.62.1] - 2022-11-01

### 🧰 Bug fixes 🧰

- Make sure filelog receiver uses file_storage for checkpointing ([#567](https://github.com/signalfx/splunk-otel-collector-chart/pull/567))

## [0.62.0] - 2022-10-28

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.62.0 ([#573](https://github.com/signalfx/splunk-otel-collector-chart/pull/573))

## [0.61.0] - 2022-10-07

### 💡 Enhancements 💡

- Increase number of queue consumers in the gateway configuration ([#554](https://github.com/signalfx/splunk-otel-collector-chart/pull/554))
- Upgrade splunk-otel-collector image to 0.61.0 ([#556](https://github.com/signalfx/splunk-otel-collector-chart/pull/556))

## [0.59.0] - 2022-09-17

### 🚀 New components 🚀

- A way to provide a custom image for init container patching host log directories ([#534](https://github.com/signalfx/splunk-otel-collector-chart/pull/534),[#535](https://github.com/signalfx/splunk-otel-collector-chart/pull/#535))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.59.1 ([#536](https://github.com/signalfx/splunk-otel-collector-chart/pull/536))
  - [BREAKING CHANGE] Datatype of `filelog.force_flush_period` and `filelog.poll_interval` were
    changed back from map to string due to upstream changes.
    See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0580-0590)

## [0.58.0] - 2022-08-24

### 💡 Enhancements 💡

- Make Openshift SecurityContextConstraints more restrictive ([#513](https://github.com/signalfx/splunk-otel-collector-chart/pull/513))
- Upgrade splunk-otel-collector image to 0.58.0 ([#518](https://github.com/signalfx/splunk-otel-collector-chart/pull/518))
  - [BREAKING CHANGE] Datatype of `filelog.force_flush_period` and `filelog.poll_interval` were
    changed from string to map due to upstream changes.
    See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0571-to-0580)

## [0.57.1] - 2022-08-05

### 💡 Enhancements 💡

- Do not send clusterReceiver metrics through gateway ([#491](https://github.com/signalfx/splunk-otel-collector-chart/pull/491))

## [0.57.0] - 2022-08-05

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.57.0 ([#504](https://github.com/signalfx/splunk-otel-collector-chart/pull/504))

## [0.56.0] - 2022-07-27

### 💡 Enhancements 💡

- Removed unnecessary change of group ownership in chmod initContainer ([#486](https://github.com/signalfx/splunk-otel-collector-chart/pull/486))
- Upgrade splunk-otel-collector image to 0.56.0 ([#501](https://github.com/signalfx/splunk-otel-collector-chart/pull/501))

## [0.55.0] - 2022-07-19

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.55.0 ([#485](https://github.com/signalfx/splunk-otel-collector-chart/pull/485))

## [0.54.2] - 2022-07-19

### 💡 Enhancements 💡

- The receiver.k8sclusterreceiver.reportCpuMetricsAsDouble feature gate has been removed ([#487](https://github.com/signalfx/splunk-otel-collector-chart/pull/487))
  - If you are using this feature gate, then see the [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0540-to-0550)
- Remove high cardinality fields from k8s events: ([#484](https://github.com/signalfx/splunk-otel-collector-chart/pull/484))
  - k8s.event.start_time
  - k8s.event.name
  - k8s.event.uid

### 🧰 Bug fixes 🧰

- Make sure that logs are enabled to send k8s events ([#481](https://github.com/signalfx/splunk-otel-collector-chart/pull/481))
- Make sure that "sourcetype" field is always set on k8s events ([#483](https://github.com/signalfx/splunk-otel-collector-chart/pull/483))

## [0.54.1] - 2022-07-01

### 🧰 Bug fixes 🧰

- Fix failing cluster receiver with enabled profiling and disabled logs ([#480](https://github.com/signalfx/splunk-otel-collector-chart/pull/480))

## [0.54.0] - 2022-06-29

### 💡 Enhancements 💡

- OTel Kubernetes receiver is now used for events collection instead of Signalfx events receiver ([#478](https://github.com/signalfx/splunk-otel-collector-chart/pull/478))
- Upgrade splunk-otel-collector image to 0.54.0 ([#479](https://github.com/signalfx/splunk-otel-collector-chart/pull/479))

### 🧰 Bug fixes 🧰

- Fix recombining of oversized log records generated by CRI-O and containerd engines ([#475](https://github.com/signalfx/splunk-otel-collector-chart/pull/475))

## [0.53.2] - 2022-06-23

### 🧰 Bug fixes 🧰

- Fix bug where clusterReceiver splunk_hec exporter is enabled but configured not to send o11y logs ([#471](https://github.com/signalfx/splunk-otel-collector-chart/pull/471))

## [0.53.1] - 2022-06-22

### 🚀 New components 🚀

- A recombine operator for OTel logs collection to reconstruct multiline logs on docker engine ([#467](https://github.com/signalfx/splunk-otel-collector-chart/pull/467))

### 💡 Enhancements 💡

- Scrape /proc/self/mountinfo in agent pods to avoid incorrect stat attempts ([#467](https://github.com/signalfx/splunk-otel-collector-chart/pull/467))
- Upgrade splunk-otel-collector image to 0.53.1 ([#468](https://github.com/signalfx/splunk-otel-collector-chart/pull/468))

## [0.53.0] - 2022-06-17

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.53.0 ([#466](https://github.com/signalfx/splunk-otel-collector-chart/pull/466))

### 🚀 New components 🚀

- Add `splunkPlatform.retryOnFailure` and `splunkPlatform.sendingQueue` config options to values.yaml ([#460](https://github.com/signalfx/splunk-otel-collector-chart/pull/460))

## [0.52.0] - 2022-06-07

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.52.2 ([#463](https://github.com/signalfx/splunk-otel-collector-chart/pull/463))

## [0.51.0] - 2022-05-24

### 🚀 New components 🚀

- Add troubleshooting documentation for incompatible Kubernetes and container runtime issues ([#452](https://github.com/signalfx/splunk-otel-collector-chart/pull/452))

### 🧰 Bug fixes 🧰

- Fix native OTel logs collection where 0 length logs cause errors after the 0.29.0 opentelemetry-logs-library changes in 0.49.0 ([#451](https://github.com/signalfx/splunk-otel-collector-chart/pull/451))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.51.0 ([#453](https://github.com/signalfx/splunk-otel-collector-chart/pull/453))

## [0.50.0] - 2022-05-03

### 🧰 Bug fixes 🧰

- Add gateway support for Host Logs ([#437](https://github.com/signalfx/splunk-otel-collector-chart/pull/437))
- Make sure that logs or profiling data is sent only when it's enabled ([#444](https://github.com/signalfx/splunk-otel-collector-chart/pull/444))
- Fix native OTel logs collection broken after the 0.29.0 opentelemetry-logs-library changes in 0.49.0 release ([#448](https://github.com/signalfx/splunk-otel-collector-chart/pull/448))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.50.0 ([#449](https://github.com/signalfx/splunk-otel-collector-chart/pull/449))

## [0.49.0] - 2022-04-28

### 💡 Enhancements 💡

- Migrate filelog operators to follow opentelemetry-log-collection v0.29.0 changes ([#436](https://github.com/signalfx/splunk-otel-collector-chart/pull/436),[#441](https://github.com/signalfx/splunk-otel-collector-chart/pull/#441))
  - [BREAKING CHANGE] Several breaking changes were made that affect the
    filelog, syslog, tcplog, and journald receivers. Any use of the
    extraFileLogs config, logsCollection.containers.extraOperators config,
    and affected receivers in a custom manner should be reviewed. See
    [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0480-to-0490)

- The receiver.k8sclusterreceiver.reportCpuMetricsAsDouble feature gate is now enabled by default ([#487](https://github.com/signalfx/splunk-otel-collector-chart/pull/487))
  - [BREAKING CHANGE] The Splunk Otel Collector has a feature gate to enable a
    bug fix that makes the k8sclusterreceiver emit a few Kubernetes cpu
    metrics differently to properly adhere to OpenTelemetry specifications. See
    [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0480-to-0490)

- Upgrade splunk-otel-collector image to 0.49.0 ([#442](https://github.com/signalfx/splunk-otel-collector-chart/pull/442))

## [0.48.0] - 2022-04-13

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.48.0 ([#434](https://github.com/signalfx/splunk-otel-collector-chart/pull/434))

## [0.47.1] - 2022-03-31

### 🧰 Bug fixes 🧰

- Bug where the k8sclusterreceiver emits a few Kubernetes cpu metrics improperly ([#419](https://github.com/signalfx/splunk-otel-collector-chart/pull/419))
  - [BREAKING CHANGE] The Splunk Otel Collector added a feature gate to enable a
    bug fix that makes the k8sclusterreceiver emit a few Kubernetes cpu
    metrics differently to properly adhere to OpenTelemetry specifications.
    See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0470-to-0471)

## [0.47.0] - 2022-03-30

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.47.1 ([#422](https://github.com/signalfx/splunk-otel-collector-chart/pull/422))

## [0.46.0] - 2022-03-17

### 🚀 New components 🚀

- Add support for otelcol feature gates to the agent, clusterReceiver, and gateway ([#410](https://github.com/signalfx/splunk-otel-collector-chart/pull/410))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.46.0 ([#413](https://github.com/signalfx/splunk-otel-collector-chart/pull/413))

## [0.45.0] - 2022-03-10

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.45.0 ([#407](https://github.com/signalfx/splunk-otel-collector-chart/pull/407))
- [BREAKING CHANGE] Use newer batch and autoscaling APIs in the Kubernetes
  cluster receiver ([#433](https://github.com/signalfx/splunk-otel-collector-chart/pull/433)). The Kubernetes cluster receiver will not be able to
  collect all the metrics it previously did for Kubernetes clusters with
  versions below 1.21 or Openshift clusters with versions below 4.8.
  See [upgrade guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0441-to-0450)

### 🧰 Bug fixes 🧰

- Bug where Prometheus errors out using default configuration on EKS and GKE ([#401](https://github.com/signalfx/splunk-otel-collector-chart/pull/401),[#405](https://github.com/signalfx/splunk-otel-collector-chart/pull/#405))

## [0.44.1] - 2022-03-08

### 🧰 Bug fixes 🧰

- Add environment processor to metrics pipeline when sending metrics to Splunk Platform ([#399](https://github.com/signalfx/splunk-otel-collector-chart/pull/399))

## [0.44.0] - 2022-03-03

### 🚀 New components 🚀

- Control plane metrics support: etcd ([#384](https://github.com/signalfx/splunk-otel-collector-chart/pull/384))

## [0.43.5] - 2022-03-02

### 🧰 Bug fixes 🧰

- Add missing splunk-otel-collector secret to gateway and cluster receiver deployment ([#390](https://github.com/signalfx/splunk-otel-collector-chart/pull/390))

## [0.43.4] - 2022-02-25

### 💡 Enhancements 💡

- [BREAKING CHANGE] Set `profilingEnabled` to default false ([#388](https://github.com/signalfx/splunk-otel-collector-chart/pull/388))

## [0.43.3] - 2022-02-24

### 🚀 New components 🚀

- Added support to collect control plane component metrics; controller-manager, coredns, proxy, scheduler ([#383](https://github.com/signalfx/splunk-otel-collector-chart/pull/383))

### 🧰 Bug fixes 🧰

- Explicitly set match_type parameter in filter processor ([#385](https://github.com/signalfx/splunk-otel-collector-chart/pull/385))
- Truncate eks/fargate cluster receiver StatefulSet names ([#386](https://github.com/signalfx/splunk-otel-collector-chart/pull/386))

## [0.43.2] - 2022-02-02

### 🚀 New components 🚀

- Support of profiling data for Splunk Observability ([#376](https://github.com/signalfx/splunk-otel-collector-chart/pull/376))

### 💡 Enhancements 💡

- [BREAKING CHANGE] OTel Collector Agent now overrides host and cloud attributes
  of logs, metrics and traces that are sent through it ([#375](https://github.com/signalfx/splunk-otel-collector-chart/pull/375)). See [upgrade
  guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0431-to-0432)

## [0.43.1] - 2022-02-01

### 🚀 New components 🚀

- `eks/fargate` distribution ([#346](https://github.com/signalfx/splunk-otel-collector-chart/pull/346))

## [0.43.0] - 2022-01-27

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.43.0 ([#370](https://github.com/signalfx/splunk-otel-collector-chart/pull/370))

## [0.42.0] - 2022-01-25

### 🚀 New components 🚀

- Journald logs collection ([#290](https://github.com/signalfx/splunk-otel-collector-chart/pull/290))
- Automatic discovery and metrics collection from the Kubernetes API server
  control plane component ([#355](https://github.com/signalfx/splunk-otel-collector-chart/pull/355))
- Native OTel logs collection from the Windows worker nodes ([#361](https://github.com/signalfx/splunk-otel-collector-chart/pull/361))
- Option to disable helm hook for custom secret validation ([#350](https://github.com/signalfx/splunk-otel-collector-chart/pull/350))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.42.0 ([#367](https://github.com/signalfx/splunk-otel-collector-chart/pull/367))

### 🧰 Bug fixes 🧰

- Double expansion issue splunk-otel-collector ([#357](https://github.com/signalfx/splunk-otel-collector-chart/pull/357)). See [upgrade
  guideline](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0410-to-0420)
- Schema validation for `image.imagePullSecrets` configuration option ([#356](https://github.com/signalfx/splunk-otel-collector-chart/pull/356))
- Schema validation for `logsCollection.containers.extraOperators` configuration
  option ([#356](https://github.com/signalfx/splunk-otel-collector-chart/pull/356))

### Removed

- Temporary helper initContainer for OTel checkpointing log path move ([#358](https://github.com/signalfx/splunk-otel-collector-chart/pull/358))

## [0.41.0] - 2021-12-13

### 🚀 New components 🚀

- Google Kubernetes Engine Autopilot support ([#338](https://github.com/signalfx/splunk-otel-collector-chart/pull/338))

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.41.0 ([#340](https://github.com/signalfx/splunk-otel-collector-chart/pull/340))

## [0.40.0] - 2021-12-08

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.40.0 ([#334](https://github.com/signalfx/splunk-otel-collector-chart/pull/334))

## [0.39.0] - 2021-11-30

[Upgrade
guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0380-to-0390)

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.39.0 ([#322](https://github.com/signalfx/splunk-otel-collector-chart/pull/322))
- [BREAKING CHANGE] Logs collection is now disabled by default for Splunk
  Observability destination ([#325](https://github.com/signalfx/splunk-otel-collector-chart/pull/325))

## [0.38.0] - 2021-11-19

This release completes the addition of content and documentation to easily allow
users to send telemetry data including logs to both Splunk observability and
Splunk platform. This will address use cases of current users of the Splunk
Connect for Kubernetes.

[Updated
README](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/README.md)

[Migration guidelines for Splunk Connect for Kubernetes
users](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/migration-from-sck.md)

[Upgrade guidelines for existing Splunk OpenTelemetry Collector for Kubernetes
users](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0371-to-0380)

### 🚀 New components 🚀

- Field name compatibility for SCK ([#258](https://github.com/signalfx/splunk-otel-collector-chart/pull/258))
- Add initContainer for file operations for running as non root user ([#263](https://github.com/signalfx/splunk-otel-collector-chart/pull/263))
- Helm hook for custom secret validation ([#294](https://github.com/signalfx/splunk-otel-collector-chart/pull/294))
- Add include logs functionality based on pod annotations ([#260](https://github.com/signalfx/splunk-otel-collector-chart/pull/260))
- Support for tailing custom host files ([#300](https://github.com/signalfx/splunk-otel-collector-chart/pull/300))

### 💡 Enhancements 💡

- Extract `container.image.tag` attribute from `container.image.name` ([#285](https://github.com/signalfx/splunk-otel-collector-chart/pull/285))
- Upgrade splunk-otel-collector image to 0.38.1 ([#284](https://github.com/signalfx/splunk-otel-collector-chart/pull/284))
- Upgrade fluentd-hec image to 1.2.8 ([#281](https://github.com/signalfx/splunk-otel-collector-chart/pull/281))
- Change secret names according to the GDI specification ([#295](https://github.com/signalfx/splunk-otel-collector-chart/pull/295))
- Make `clusterName` configuration parameter generally required ([#296](https://github.com/signalfx/splunk-otel-collector-chart/pull/296))
- Changed the default checkpoint path to `/var/addon/splunk/otel_pos` ([#292](https://github.com/signalfx/splunk-otel-collector-chart/pull/292))
- Rename "provider" and "distro" parameters to "cloudProvider" and
  "distribution" ([#297](https://github.com/signalfx/splunk-otel-collector-chart/pull/297))
- Changed SplunkPlatform properties to match helm best practices. ([#306](https://github.com/signalfx/splunk-otel-collector-chart/pull/306))
- Rename parameter groups for Splunk OTel Collector components ([#301](https://github.com/signalfx/splunk-otel-collector-chart/pull/301)):
  - `otelAgent` -> `agent`
  - `otelCollector` -> `gateway`
  - `otelK8sClusterReceiver` -> `clusterReceiver`
- Rename `stream` log attribute to `log.iostream` ([#311](https://github.com/signalfx/splunk-otel-collector-chart/pull/311))
- Improve configuration for fetching attributes from annotations and labels of
  pods and namespaces ([#273](https://github.com/signalfx/splunk-otel-collector-chart/pull/273))
- Use `main` as default index and disable metrics by default for Splunk
  Platform ([#305](https://github.com/signalfx/splunk-otel-collector-chart/pull/305))

### 🧰 Bug fixes 🧰

- Splunk Platform client certificates ([#286](https://github.com/signalfx/splunk-otel-collector-chart/pull/286))
- `logsCollection.containers.excludePaths` config parameter ([#312](https://github.com/signalfx/splunk-otel-collector-chart/pull/312))
- Splunk Platform sourcetype precedence order ([#276](https://github.com/signalfx/splunk-otel-collector-chart/pull/276))

### Removed

- Busybox image dependency ([#275](https://github.com/signalfx/splunk-otel-collector-chart/pull/275))
- `extraArgs` config parameter ([#313](https://github.com/signalfx/splunk-otel-collector-chart/pull/313))

## [0.37.1] - 2021-11-01

### 🚀 New components 🚀

- Add initContainer for log checkpoint migration from Fluentd to Otel agent ([#253](https://github.com/signalfx/splunk-otel-collector-chart/pull/253))
- Add index routing for Splunk Enterprise/Cloud customers ([#256](https://github.com/signalfx/splunk-otel-collector-chart/pull/256))

### 🧰 Bug fixes 🧰

- Fix metrics/logs disabling for Splunk Platform destination ([#259](https://github.com/signalfx/splunk-otel-collector-chart/pull/259))
- Fix kubernetes events in Observability IMM by adding `kubernetes_cluster`
  attribute ([#261](https://github.com/signalfx/splunk-otel-collector-chart/pull/261))

## [0.37.0] - 2021-10-26

[Upgrade
guidelines](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0362-to-0370)

### 🚀 New components 🚀

- Add recommended Kubernetes labels ([#217](https://github.com/signalfx/splunk-otel-collector-chart/pull/217))
- Add an option to skip RBAC resources creation ([#231](https://github.com/signalfx/splunk-otel-collector-chart/pull/231))
- Enable container metadata. This gives all collected logs new attributes:
  `container.image.name` and `container.image.tag`. Also the native OTel logs
  collection gets `container.id` attribute that allows container level
  correlation in Splunk Observability Cloud closing a feature parity gap with
  fluentd ([#238](https://github.com/signalfx/splunk-otel-collector-chart/pull/238))
- Add strict values.yaml schema validation ([#227](https://github.com/signalfx/splunk-otel-collector-chart/pull/227),[#234](https://github.com/signalfx/splunk-otel-collector-chart/pull/#234),[#239](https://github.com/signalfx/splunk-otel-collector-chart/pull/#239))

### 💡 Enhancements 💡

- BREAKING CHANGE: Reorder resource detectors, moving the `system` detector
  to the end of the list. Applying this change in an EC2 or Azure environment
  may change the `host.name` dimension and the resource ID dimension
  on some MTSes, possibly causing detectors to fire.
- BREAKING CHANGE: Reduce scope of host mounted volumes on linux systems ([#232](https://github.com/signalfx/splunk-otel-collector-chart/pull/232))
- Change `run_id` log resource attribute to `k8s.container.restart_count` ([#226](https://github.com/signalfx/splunk-otel-collector-chart/pull/226))
- Use only `splunkPlatform.endpoint` and `splunkObservability.realm` parameters
  to identify which destination is enabled, remove default value for
  `splunkObservability.realm` ([#230](https://github.com/signalfx/splunk-otel-collector-chart/pull/230),[#233](https://github.com/signalfx/splunk-otel-collector-chart/pull/#233))
- Upgrade splunk-otel-collector image to 0.37.1 ([#237](https://github.com/signalfx/splunk-otel-collector-chart/pull/237),[#249](https://github.com/signalfx/splunk-otel-collector-chart/pull/#249))
- Simplify configuration for switching to native OTel logs collection ([#246](https://github.com/signalfx/splunk-otel-collector-chart/pull/246))

### 🧰 Bug fixes 🧰

- Fix setting of SPLUNK_MEMORY_TOTAL_MIB env var in otelAgent daemonset ([#240](https://github.com/signalfx/splunk-otel-collector-chart/pull/240))
- Enable OTLP HTTP ports (4318 and 55681) in otelAgent daemonset ([#243](https://github.com/signalfx/splunk-otel-collector-chart/pull/243))

## [0.36.2] - 2021-10-08

### 🧰 Bug fixes 🧰

- Exclude redundant `groupbyattrs/logs` processor from native logs collection
  pipeline ([#219](https://github.com/signalfx/splunk-otel-collector-chart/pull/219))
- Fix deprecation messages for old `<telemetry>Enabled` parameters ([#220](https://github.com/signalfx/splunk-otel-collector-chart/pull/220))

## [0.36.1] - 2021-10-07

### 🧰 Bug fixes 🧰

- Fix backward compatibility for `splunkRealm` parameter ([#218](https://github.com/signalfx/splunk-otel-collector-chart/pull/218))

## [0.36.0] - 2021-10-06

### 🚀 New components 🚀

- Support k8s clusters with Windows nodes ([#190](https://github.com/signalfx/splunk-otel-collector-chart/pull/190))

### 💡 Enhancements 💡

- Change configuration interface to be able to send data to Splunk
  Enterprise/Cloud and to Splunk Observability ([#209](https://github.com/signalfx/splunk-otel-collector-chart/pull/209))
- Improve multiline logs configuration for native logs collection ([#208](https://github.com/signalfx/splunk-otel-collector-chart/pull/208))

## [0.35.3] - 2021-09-29

### 🚀 New components 🚀

- Add an option to provide additional custom RBAC rules ([#206](https://github.com/signalfx/splunk-otel-collector-chart/pull/206))

## [0.35.2] - 2021-09-28

### 🚀 New components 🚀

- Send k8s events additionally to Splunk HEC endpoint ([#202](https://github.com/signalfx/splunk-otel-collector-chart/pull/202))

## [0.35.1] - 2021-09-23

### 🚀 New components 🚀

- Add support for OpenShift distribution ([#196](https://github.com/signalfx/splunk-otel-collector-chart/pull/196))
- Add native OTel logs collection as an option ([#197](https://github.com/signalfx/splunk-otel-collector-chart/pull/197))

### Removed

- Remove PodSecurityPolicy installation option ([#195](https://github.com/signalfx/splunk-otel-collector-chart/pull/195))

## [0.35.0] - 2021-09-17

### 🚀 New components 🚀

- Add an option to collect k8s events with smartagent/kubernetes-events receiver ([#187](https://github.com/signalfx/splunk-otel-collector-chart/pull/187))

### 💡 Enhancements 💡

- Move k8s metadata enrichment from fluentd to otel-collector ([#192](https://github.com/signalfx/splunk-otel-collector-chart/pull/192))

## [0.31.0] - 2021-08-10

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.31.0 ([#183](https://github.com/signalfx/splunk-otel-collector-chart/pull/183))
- Set more frequent checks for memory_limiter ([#178](https://github.com/signalfx/splunk-otel-collector-chart/pull/178))
- Make Fluentd init container image variable ([#182](https://github.com/signalfx/splunk-otel-collector-chart/pull/182))

### 🧰 Bug fixes 🧰

- All missing attributes are added to prometheus metrics reported
  by gateway and k8s-cluster-receiver collector deployments ([#170](https://github.com/signalfx/splunk-otel-collector-chart/pull/170))
- Fix pod affinity setting ([#181](https://github.com/signalfx/splunk-otel-collector-chart/pull/181))

## [0.29.1] - 2021-07-09

### 🧰 Bug fixes 🧰

- Fix generation of service.name log attribute in istio environment ([#176](https://github.com/signalfx/splunk-otel-collector-chart/pull/176))

## [0.29.0] - 2021-07-08

### 💡 Enhancements 💡

- Change internal metrics port from 8888 to 8889 ([#172](https://github.com/signalfx/splunk-otel-collector-chart/pull/172))
- Upgrade splunk-otel-collector image version to 0.29.0 ([#174](https://github.com/signalfx/splunk-otel-collector-chart/pull/174))

## [0.28.2] - 2021-07-07

### 🚀 New components 🚀

- Add Istio specific configurations ([#171](https://github.com/signalfx/splunk-otel-collector-chart/pull/171))
- Enable OTLP receiver in logs pipeline ([#167](https://github.com/signalfx/splunk-otel-collector-chart/pull/167))

### Removed

- BREAKING: Remove SAPM receiver from default config ([#168](https://github.com/signalfx/splunk-otel-collector-chart/pull/168))

## [0.28.1] - 2021-06-18

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.28.1 ([#166](https://github.com/signalfx/splunk-otel-collector-chart/pull/166))

## [0.28.0] - 2021-06-16

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector image to 0.28.0 ([#164](https://github.com/signalfx/splunk-otel-collector-chart/pull/164))

## [0.27.0] - 2021-06-15

### 💡 Enhancements 💡

- BREAKING CHANGE: Auto-detection of prometheus metrics is disabled by default ([#163](https://github.com/signalfx/splunk-otel-collector-chart/pull/163)). See
  [Upgrade guideline](https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0264-to-0270)

## [0.26.4] - 2021-06-09

### 🧰 Bug fixes 🧰

- Fix container runtime detection when metrics pipeline disabled ([#161](https://github.com/signalfx/splunk-otel-collector-chart/pull/161))

## [0.26.3] - 2021-06-08

- Add an option to add extra labels to pods ([#158](https://github.com/signalfx/splunk-otel-collector-chart/pull/158))
- Add an option to add extra annotations to deployments, daemonset, pods and service account ([#158](https://github.com/signalfx/splunk-otel-collector-chart/pull/158))
- Add an option to mount extra volumes to gateway-mode and k8s cluster receiver collectors ([#157](https://github.com/signalfx/splunk-otel-collector-chart/pull/157))

## [0.26.2] - 2021-05-28

### 💡 Enhancements 💡

- Automatically detect container runtime using initContainers and apply
  relevant parsing config instead of asking user to specify criTimeFormat.
  This is an important change to enable smooth transition from deprecated docker
  to containerd runtime ([#154](https://github.com/signalfx/splunk-otel-collector-chart/pull/154))

## [0.26.1] - 2021-05-25

### 🚀 New components 🚀

- Add an option to mount extra volumes using `otelAgent.extraVolumes` and `otelAgent.extraVolumeMounts` ([#151](https://github.com/signalfx/splunk-otel-collector-chart/pull/151))

## [0.26.0] - 2021-05-21

### 🚀 New components 🚀

- Add signalfx metrics receiver to the agent ([#136](https://github.com/signalfx/splunk-otel-collector-chart/pull/136))

### 💡 Enhancements 💡

- fluentd logs are now sent through the collector instead of being sent directly to the backend ([#109](https://github.com/signalfx/splunk-otel-collector-chart/pull/109))
- Logs are sent through the OpenTelemetry Agent on the local node by default. `otelAgent.enabled` value must be set to `true` when using logs ([#127](https://github.com/signalfx/splunk-otel-collector-chart/pull/127))
- `otelAgent.ports` and `otelCollector.ports` are selectively enabled depending on what telemetry types are enabled with `metricsEnabled`, `tracesEnabled`, and `logsEnabled`
- Removed setting `host.name` through the `resource` processor as it is already set by the `resourcedetection/system` processor
- Upgraded to Splunk OpenTelemetry Collector 0.26.0
- Kubernetes cluster metrics now have a dimension `receiver:k8scluster` to ensure that
  MTS do not conflict with Kubernetes metrics sent by Smart Agent for the same cluster. ([#134](https://github.com/signalfx/splunk-otel-collector-chart/pull/134))

### Removed

- Removed `ingestHost`, `ingestPort`, `ingestProtocol`, use `ingestUrl` instead ([#123](https://github.com/signalfx/splunk-otel-collector-chart/pull/123))
- Removed `logsBackend`, configure `splunk_hec` exporter directly ([#123](https://github.com/signalfx/splunk-otel-collector-chart/pull/123))
- Removed `splunk.com/index` annotation for logs ([#123](https://github.com/signalfx/splunk-otel-collector-chart/pull/123))
- Removed `fluentd.config.indexFields` as all fields sent are indexed ([#123](https://github.com/signalfx/splunk-otel-collector-chart/pull/123))
- Removed `fluentforward` receiver from gateway ([#127](https://github.com/signalfx/splunk-otel-collector-chart/pull/127))
- Removed `service.ports`, sourced from `otelCollector.ports` instead ([#140](https://github.com/signalfx/splunk-otel-collector-chart/pull/140))

## [0.25.0] - 2021-05-07

### 💡 Enhancements 💡

- Upgrade splunk-otel-collector docker image to 0.25.0 ([#131](https://github.com/signalfx/splunk-otel-collector-chart/pull/131))

### 🚀 New components 🚀

- Pre-rendered manifests can be found in [rendered](rendered) directory

## [0.24.13] - 2021-05-04

### 💡 Enhancements 💡

- Remove internal fluentd metrics sent as logs with monitor_agent. Prometheus
  metrics exposed on 0.0.0.0:24231 should be used instead ([#122](https://github.com/signalfx/splunk-otel-collector-chart/pull/122))

## [0.24.12] - 2021-05-03

### 🧰 Bug fixes 🧰

- Fix logs collection configuration for CRI-O / containerd runtimes ([#120](https://github.com/signalfx/splunk-otel-collector-chart/pull/120))

## [0.24.11] - 2021-04-29

### 💡 Enhancements 💡

- Change the way to configure "concat" filter for container logs ([#117](https://github.com/signalfx/splunk-otel-collector-chart/pull/117))

## [0.24.10] - 2021-04-21

### 💡 Enhancements 💡

- Disable fluentd metrics collection by default ([#108](https://github.com/signalfx/splunk-otel-collector-chart/pull/108))

## [0.24.9] - 2021-04-18

### 💡 Enhancements 💡

- Change OTLP port from deprecated 55680 to default 4317 ([#103](https://github.com/signalfx/splunk-otel-collector-chart/pull/103))

### 🧰 Bug fixes 🧰

- Open port for signalfx-forwarder on the agent ([#106](https://github.com/signalfx/splunk-otel-collector-chart/pull/106))

## [0.24.8] - 2021-04-16

### 🧰 Bug fixes 🧰

- Fix traces enrichment with k8s metadata ([#102](https://github.com/signalfx/splunk-otel-collector-chart/pull/102))

## [0.24.7] - 2021-04-15

### 💡 Enhancements 💡

- Switch to stable Splunk OTel Collector image 0.24.3 ([#100](https://github.com/signalfx/splunk-otel-collector-chart/pull/100))

## [0.24.6] - 2021-04-15

### 🚀 New components 🚀

- Enable smartagent/signalfx-forwarder in the default agent trace pipeline ([#98](https://github.com/signalfx/splunk-otel-collector-chart/pull/98))

## [0.24.5] - 2021-04-13

### 🚀 New components 🚀

- Enable batch processor in the default metrics pipelines ([#90](https://github.com/signalfx/splunk-otel-collector-chart/pull/90))

### 💡 Enhancements 💡

- Ensure all metrics and traces are routed through the gateway deployment if
  it's enabled ([#96](https://github.com/signalfx/splunk-otel-collector-chart/pull/96))

## [0.24.4] - 2021-04-12

### 🚀 New components 🚀

- Add an option to set extra environment variables ([#91](https://github.com/signalfx/splunk-otel-collector-chart/pull/91))

## [0.24.3] - 2021-04-12

### 🧰 Bug fixes 🧰

- Fix resource attribute in the default traces pipeline ([#88](https://github.com/signalfx/splunk-otel-collector-chart/pull/88))
- Add metric_source:kubernetes for all k8s cluster metrics ([#89](https://github.com/signalfx/splunk-otel-collector-chart/pull/89))
- Fix host.name attribute in logs ([#87](https://github.com/signalfx/splunk-otel-collector-chart/pull/87))

## [0.24.2] - 2021-04-07

### 🚀 New components 🚀

- Add host.name attribute to logs ([#86](https://github.com/signalfx/splunk-otel-collector-chart/pull/86))

## [0.24.1] - 2021-04-07

### 💡 Enhancements 💡

- Remove deprecated opencensus receiver ([#85](https://github.com/signalfx/splunk-otel-collector-chart/pull/85))

## [0.24.0] - 2021-04-07

### 💡 Enhancements 💡

- Upgrade image to 0.24.0 version ([#84](https://github.com/signalfx/splunk-otel-collector-chart/pull/84))
- Add system detector to default metrics and traces pipelines ([#84](https://github.com/signalfx/splunk-otel-collector-chart/pull/84))