splunk-otel-collector-0.122.1

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

🛑 Breaking changes 🛑

• logs: Disable migrateCheckpoint by default and introduce a new option migrateLogsCheckpoints to enable it if needed. (#1757)
• agent: Remove smartagent/signalfx-forwarder from the agent default config. (#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)

💡 Enhancements 💡

• agent: Allow featureGates.useControlPlaneMetricsHistogramData to work with any distribution of k8s cluster. (#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)
• all: Add useMemoryLimitPercentage feature gate (#1761)

🧰 Bug fixes 🧰

• clusterReceiver: Removes k8sattributes processor from Splunk Observability events pipeline which is enabled by the chart config infrastructureMonitoringEventsEnabled. (#1746)

splunk-otel-collector-0.122.0

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

🧰 Bug fixes 🧰

• agent/gateway: Ensure entity events are sent via gateway if enabled. (#1732)
• clusterReceiver: Removes warning from chart when the clusterReceiver.eventsEnabled flag is set to true. (#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.

splunk-otel-collector-0.121.0

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

🧰 Bug fixes 🧰

• other: Fixed updating metrics' sourcetype with annotations (#1375)

splunk-otel-collector-0.120.1

💡 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)
  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)
• 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)
• all: Restore values of service.name resource attribute for internal metrics changed in 0.120.0 (#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.

splunk-otel-collector-0.120.0

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

🛑 Breaking changes 🛑

• operator: Migrate the operator to use Helm generated TLS certificates instead of cert-manager by default (#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.
  • If you use .Values.operator.enabled=true and .Values.certmanager.enabled=true, please review the upgrade guidelines.

💡 Enhancements 💡

• operator: Bump operator to 0.80.2 in helm-charts/splunk-otel-collector/Chart.yaml (#1678)

splunk-otel-collector-0.119.0

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

💡 Enhancements 💡

• chart: Enable support for custom propagators in spec.propagators within Instrumentation Configuration. (#1663)
  This change allows users to specify custom propagators in spec.propagators when configuring OpenTelemetry Instrumentation.
  This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.119.0.

🚩 Deprecations 🚩

• clusterReceiver: Deprecate the securityContext field in favor of the podSecurityContext. (#1647)
• gateway: Deprecate the securityContext field in favor of the podSecurityContext. (#1647)

💡 Enhancements 💡

• clusterReceiver: Add an option to set the security context for the container. (#1647)
• gateway: Add an option to set the security context for the container. (#1647)
• operator: Bump dotnet to v1.9.0 in helm-charts/splunk-otel-collector/values.yaml (#1651)
• operator: Bump java to v2.13.0 in helm-charts/splunk-otel-collector/values.yaml (#1669)

splunk-otel-collector-0.118.0

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

💡 Enhancements 💡

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

splunk-otel-collector-0.117.0

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

Important

If upgrading from a version older than 0.116.0, please review the upgrade guidelines for details about potential breaking changes.

⚠️ Known issues ⚠️

The sh executable that ships as part of the Docker image of the collector is corrupted in this release.

This affects users who set the secret.create setting to false. As a workaround, users can set secret.validateSecret to false to avoid running into errors when deploying the chart.

💡 Enhancements 💡

• operator: Bump java to v2.11.0 in helm-charts/splunk-otel-collector/values.yaml (#1608)

splunk-otel-collector-0.116.0

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

🛑 Breaking changes 🛑

• operator: Move operator CRD installation to the crds/ folder via a subchart to resolve Helm install ordering issues (#1561,#1619)
  • Users enabling the operator (.Values.operator.enabled=true) must now set operatorcrds.install=true in Helm values or manually manage CRD installation.
  • 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.
  • If you use operator.enabled=true you may have to follow some migration steps, please see the Upgrade guidelines.

💡 Enhancements 💡

• collector: Document the possible use of a FIPS-140 compliant image (#1582)
• clusterReceiver: Configure k8s attributes processor for cluster receiver to ingest events into index defined in namespace annotation (#1481)
• agent: Make it so the default tolerations used to deploy the agent collector account for k8s distribution (#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)
• operator: Bump java to v2.10.0 in helm-charts/splunk-otel-collector/values.yaml (#1551)
• operator: Bump nodejs to v2.15.0 in helm-charts/splunk-otel-collector/values.yaml (#1558)
• agent, clusterReceiver, gateway: Update config for scraping internal metrics to use new config interface and loopback address. (#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)
• gateway: add signalfx exporter to the gateway traces pipeline to enable APM correlation (#1607)

splunk-otel-collector-0.113.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector 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)
• agent: Exclude scraping filesystem metrics from mounts that are not accessible from inside the container to avoid scraping errors. (#1550)