releases.shpreview

0.97.0

$npx @buildinternet/releases show rel_I1IFfkiCRHODWLoOs3t8k

What's Changed

Additional Notes: This replaces the Dash0 injector binary built from this repository (images/instrumentation/injector) with the OpenTelemetry injector binary produced and released from the upstream project, https://github.com/open-telemetry/opentelemetry-injector. This is part of an ongoing effort to make the component formerly known as the Dash0 injector available and more accessible to the wider OpenTelemetry ecosystem. For all intents and purposes, the current incarnation of https://github.com/open-telemetry/opentelemetry-injector is a copy of the sources from this repository, that is, the OpenTelemetry injector is the Dash0 Injector, just under a new name.

BREAKING CHANGES:

  • If you use the Dash0 operator to manage check rules, the "origin" (i.e. the ID) of each check rule will change with this upgrade. As a result, any currently failing checks will be resolved with the operator upgrade and replaced by new failing checks with the new origin. This is a one-time event when upgrading to 0.97.0. (See PR 703 for more details.)
  • Workloads that previously used DASH0_INJECTOR_LOG_LEVEL to configure the injector's log level (e.g. DASH0_INJECTOR_LOG_LEVEL=none or similar) now need to use OTEL_INJECTOR_LOG_LEVEL instead. The log level values are unchanged (debug, info, warn, error, none). If the variable is set in the Kubernetes manifest (e.g. pod spec template -> container -> env), the operator will automatically translate the name. If the environment variable is added via other means (e.g. in the Dockerfile), this needs to be updated manually.

Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.96.0...0.97.0

Fetched May 1, 2026