splunk-otel-collector-0.109.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.109.0.

🛑 Breaking changes 🛑

• operator: Operator Helm values previously under .Values.operator.instrumentation.spec.* have been moved to .Values.instrumentation.* (#1436)
  If you use custom values under .Values.operator.instrumentation.spec.* please review the upgrade guidelines

💡 Enhancements 💡

• agent: Added fsyncFlag configuration to allow users to enable fsync on the filestorage. (#1425)
• agent: Add a feature gate useControlPlaneMetricsHistogramData (#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)
  The new continuous discovery mechanism is disabled by default. To enable it, set the following values in your configuration:

  agent:
    discovery:
      enabled: true
    featureGates: splunk.continuousDiscovery

• operator: Bump nodejs to v2.12.0 in helm-charts/splunk-otel-collector/values.yaml (#1434)

🧰 Bug fixes 🧰

• targetAllocator: Fix the name of the service account token given when featureGates.explicitMountServiceAccountToken is true (#1427)

splunk-otel-collector-0.105.5

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

💡 Enhancements 💡

• all: Offer an experimental feature gate to mount service tokens in specific containers. (#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.

splunk-otel-collector-0.105.4

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector 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)
  This is a major upgrade. If you use Java auto-instrumentation please review the upgrade guidelines

🧰 Bug fixes 🧰

• agent: Retry indefinitely on filelog receiver if noDropLogsPipeline feature gate is enabled. (#1410)

splunk-otel-collector-0.105.3

[0.105.3] - 2024-08-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

🛑 Breaking changes 🛑

• agent: Remove the deprecated OTLP HTTP port 55681 (#1359)

🚀 New components 🚀

• targetAllocator: Add support for Target Allocator as part of the Helm chart. (#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 💡

• operator: Bump nodejs to v2.11.0 in helm-charts/splunk-otel-collector/values.yaml (#1352)
• agent: Add an experimental feature gate to use exporter batching instead of the batch processor (#1387)
• all: Set automountServiceAccountToken to true explicitly for the chart's defined service accounts. (#1390)
• operator: Bump java to v1.32.3 in helm-charts/splunk-otel-collector/values.yaml (#1355)

🧰 Bug fixes 🧰

• agent: Remove apparmor pod annotation by enabled default (#1378)

splunk-otel-collector-0.105.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

splunk-otel-collector-0.104.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.104.0.

💡 Enhancements 💡

• operator: Bump nodejs to v2.9.0 in helm-charts/splunk-otel-collector/values.yaml (#1337)

splunk-otel-collector-0.103.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.103.0.

💡 Enhancements 💡

• operator: Bump dotnet to v1.6.0 in helm-charts/splunk-otel-collector/values.yaml (#1327)
• operator: Bump java to v1.32.2 in helm-charts/splunk-otel-collector/values.yaml (#1328)

🧰 Bug fixes 🧰

• chart: Updated Security Context Constraints for OpenShift support to fix formatting issues and add support for the operator service account (#1325)

splunk-otel-collector-0.102.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.102.1.

💡 Enhancements 💡

• agent: Add a pod annotation that designates the otel-collector as unconfined for appArmor-protected environments (#1313)

splunk-otel-collector-0.101.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.101.0.

💡 Enhancements 💡

• operator: Bump java to v1.32.1 in helm-charts/splunk-otel-collector/values.yaml (#1300)

🧰 Bug fixes 🧰

• operator: Fix issue where SPLUNK_OTEL_AGENT env var was set before custom operator.instrumentation.spec.env env vars (#1292)

splunk-otel-collector-0.99.1

💡 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)
• operator: Bump dotnet to v1.5.0 in helm-charts/splunk-otel-collector/values.yaml (#1282)