This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.136.1.
🛑 Breaking changes 🛑
clusterReceiver
: Remove thek8sattributesprocessor
from theclusterReceiver
logs pipeline to fix incorrect enrichment of Kubernetes object and event data. (#2075)- The
k8sattributesprocessor
was previously misconfigured in theclusterReceiver
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 includecontainer.id
,container.image.name
, andcontainer.image.tag
attributes. - Events from the
k8sobjects
receiver will no longer have anyk8s.pod.*
orcontainer.*
attributes exceptk8s.namespace.name
(when applicable) andk8s.resource.name
- Events from the
- 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.
- The
💡 Enhancements 💡
opentelemetry-operator-crds
: Bump subchart opentelemetry-operator-crds to 0.0.5. Refer to further instructions for updating CRDs if using option. (#2091)operator
: Bump operator to 0.95.3 in helm-charts/splunk-otel-collector/Chart.yaml (#2091)
🧰 Bug fixes 🧰
agent
: Skip os-release mount for GKE (#2089)