0.94.0

What's Changed

• fix(collectors): set resourcedetection.*.node_from_env_var explicitly by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/692
• feat(workloads): do not replace existing OTEL_EXPORTER_OTLP_* settings by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/690
• feat(workloads): add per-container instrumentation issues to events by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/690
• chore(deps): bump the production-dependencies group across 2 directories with 4 updates by @dependabot[bot] in https://github.com/dash0hq/dash0-operator/pull/683
• test: add unit tests for targetallocator_manager by @ten15bit in https://github.com/dash0hq/dash0-operator/pull/687
• chore(deps): bump @dash0/opentelemetry from 3.0.10 to 3.0.11 in /images/instrumentation/node.js by @dependabot[bot] in https://github.com/dash0hq/dash0-operator/pull/689

Action Required

Previously, the Dash0 operator would overwrite OTEL_EXPORTER_OTLP_ENDPOINT (and OTEL_EXPORTER_OTLP_PROTOCOL) for each container when instrumenting workloads, without regard for existing settings. This no longer happens. If the operator finds that a container sets either of these environment variables, the operator will not overwrite them. If your workloads define OTEL_EXPORTER_OTLP_ENDPOINT and/or OTEL_EXPORTER_OTLP_PROTOCOL and you relied on the operator to overwrite it to route telemetry to the Dash0 operator's OpenTelemetry collectors, make sure to remove the OTEL_EXPORTER_OTLP_ENDPOINT/OTEL_EXPORTER_OTLP_PROTOCOL from the workload manifest.

Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.93.2...0.94.0