This release fixes some issues that can occur when upgrading to 0.102.0.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.102.0...0.102.1
Starting with this release, the export field in both the Dash0OperatorConfiguration and Dash0Monitoring resources has been marked as deprecated since it has been replaced by exports. We automatically migrate export to exports in the mutating webhook to avoid breaking existing setups, but we recommend that you eventually move to the new exports field.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.101.1...0.102.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.101.0...0.101.1
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.100.0...0.101.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.99.1...0.100.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.99.0...0.99.1
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.98.0...0.99.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.97.0...0.98.0
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:
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
Starting with this release, a Dash0OperatorConfiguration with a valid export config is required and will serve as default when exporting telemetry.
It is possible to overwrite the export per-namespace by providing a custom export in a namespace's Dash0Monitoring resource.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.95.1...0.96.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.95.0...0.95.1
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.94.0...0.95.0
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
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.93.1...0.93.2
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.93.0...0.93.1
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.92.1...0.93.0
This Dash0 operator release allows setting GOMEMLIMIT for the operator manager. This setting was missing previously. This allows to better protect the operator from OutOfMemory errors. Since this is a new setting, its default value (205MiB) is set with respect to the operator’s default value for its own Kubernetes memory limit.
If you have set a custom operator.managerContainerResources.limits.memory you should also set a matching operator.managerContainerResources.gomemlimit value. We recommend to set gomemlimit to around 80% of limits.memory.
If you leave the default gomemlimit in place and have a higher limits.memory setting, Golang’s garbage collection might spend more CPU cycles than necessary.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.92.0...0.92.1
This Dash0 operator release allows setting GOMEMLIMIT for the operator manager. This setting was missing previously. This allows to better protect the operator from OutOfMemory errors. Since this is a new setting, its default value (205MiB) is set with respect to the operator’s default value for its own Kubernetes memory limit.
If you have set a custom operator.managerContainerResources.limits.memory you should also set a matching operator.managerContainerResources.gomemlimit value. We recommend to set gomemlimit to around 80% of limits.memory.
If you leave the default gomemlimit in place and have a higher limits.memory setting, Golang’s garbage collection might spend more CPU cycles than necessary.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.91.0...0.92.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.90.0...0.91.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.89.0...0.90.0