Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.73.0...0.74.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.72.0...0.73.0
Beginning with version 0.71.0, the Dash0 operator version a new resource version (v1beta1) for the Dash0 monitoring resource. This should be completely transparent for you as an operator user, no action required. The current resource version v1alpha1 is still supported, and there are no plans to remove support for that version. More information on this CRD version update can be found here.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.71.0...0.72.0
This Dash0 operator version includes a new resource version (v1beta1) for the Dash0 monitoring resource. This should be completely transparent for you as an operator user, no action required. The current resource version v1alpha1 is still supported, and there are no plans to remove support for that version. More information on this CRD version update can be found here.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.70.3...0.71.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.70.2...0.70.3
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.70.1...0.70.2
NODE_OPTIONS setting, which clashed with the recent move of the Dash0 Node.js OpenTelemetry distribution from npm scope @dash0hq to @dash0.Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.70.0...0.70.1
IMPORTANT: Please do not use release 0.70.0 if you have Node.js workloads in your cluster and you have also used operator version 0.27.0 or lower in that cluster. Update to release 0.70.1 or later directly instead.
OTEL_RESOURCE_ATTRIBUTES environment variable or by adding the system property -Dotel.resource.attributes to the JAVA_TOOL_OPTIONS environment variable. The Java OTel SDK will ignore OTEL_RESOURCE_ATTRIBUTES if -Dotel.resource.attributes is set. The Dash0 injector will add -Dotel.resource.attributes to JAVA_TOOL_OPTIONS to add useful Kubernetes-related resource attributes like pod uid, pod name etc. This would accidentally discard the user-provided OTEL_RESOURCE_ATTRIBUTES key-value pairs. This fix makes the injector merge the values from OTEL_RESOURCE_ATTRIBUTES into -Dotel.resource.attributes in situations where this is appropriate.Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.69.1...0.70.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.69.0...0.69.1
feat: allow IAC operations without telemetry collection by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/437: This adds a new configuration setting to the operator configuration resource: telemetryCollection.enabled. The setting defaults to true. When set to false, all telemetry collection is disabled and no OpenTelemetry collectors are deployed by the operator. This can be useful when the only purpose of using the Dash0 operator is to use it for its infrastructure-as-code capabilities, that is, synchronizing Perses dashboard and Prometheus rule resources to the Dash0 API.
chore(deps): bump the production-dependencies group by @dependabot in https://github.com/dash0hq/dash0-operator/pull/428, https://github.com/dash0hq/dash0-operator/pull/435
chore(deps): bump the production dependencies of the Dash0 collector image by @github-actions in https://github.com/dash0hq/dash0-operator/pull/436
chore(deps): bump @dash0hq/opentelemetry from 2.0.5 to 2.0.7 in /images/instrumentation/node.js by @dependabot in https://github.com/dash0hq/dash0-operator/pull/425, https://github.com/dash0hq/dash0-operator/pull/432
chore(deps): bump io.opentelemetry.javaagent:opentelemetry-javaagent from 2.16.0 to 2.17.0 in /images/instrumentation/jvm by @dependabot in https://github.com/dash0hq/dash0-operator/pull/426
chore(deps): bump github.com/perses/perses-operator from 0.1.12 to 0.2.0 in the production-dependencies group across 1 directory by @dependabot in https://github.com/dash0hq/dash0-operator/pull/421
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.68.0...0.69.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.67.0...0.68.0
BREAKING CHANGE: The removal of the default resource requests for the init container is a breaking change if you actually want resource requests for the Dash0 instrumentation init container and you are currently relying on the default resource requests instead of defining explicit values for the Helm chart via operator.initContainerResources.requests. To remedy this, set explicit resource requests for the init container before installing this release.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.66.0...0.67.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.65.0...0.66.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.64.0...0.65.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.63.0...0.64.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.62.0...0.63.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.61.1...0.62.0
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.61.0...0.61.1
This is the first release that comes with a complete rewrite of the (previously C-based) Dash0 injector in Zig. This rewrite will enable adding auto-tracing support for new runtimes faster, and safer.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.60.0...0.61.0
BREAKING CHANGES: This release contains breaking changes, if you are deploying a Dash0Monitoring with an instrumentWorkloads other than none to the namespace kube-system or kube-node-lease. Set the instrumentWorkloads for that Dash0Monitoring to none instead.
Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.59.0...0.60.0