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 setoperatorcrds.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.
- Users enabling the operator (
💡 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 defaultoperator
: 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
andserver.address