0.59.0

What's Changed

• feat: configure log collection per namespace, independent of instrumentation by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/351
• feat: collect all pod labels and annotations as resource attributes, with prefixes "k8s.pod.label." and "k8s.pod.annotation." respectively, can be disabled per cluster via the operator configuration resource by @basti1302 in https://github.com/dash0hq/dash0-operator/pull/351

Starting with this release, log collection is now enabled for all all workloads in monitored namespaces, independent of whether they have been instrumented (that is, independent of the pod having been instrumented. Log collection can also be disabled per namespace via the monitoring resource.

BREAKING CHANGES: The log collection change is a breaking change in the following ways:

• If you have namespaces with a Dash0 monitoring resource with instrumentWorkloads: none, no logs from these namespaces would be collected. Starting with this release, logs from all pods in those namespaces will be collected, since spec.logCollection.enabled in the monitoring resource defaults to true. To avoid collecting these additional logs, set spec.logCollection.enabled=false for all namespaces for which log collection is not desired when upgrading to this release.
• You can no longer control log collection for individual workloads via Kubernetes labels on workloads. Previously, pod logs from workloads that had the label dash0.com/enable=false would not be collected. Now logs from all pods in a namespace will be collected if log collection is enabled for that namespace, independently of the dash0.com/enable label. You can use a filter expression in the monitoring resource to drop logs from pods that you are not interested in.

This release also introduces two more (backward compatible) changes to the Dash0 custom resource types:

• The setting Dash0Monitoring.spec.prometheusScrapingEnabled is deprecated. Please use Dash0Monitoring.spec.prometheusScraping.enabled instead. (The deprecated option still works though, it might be removed in a future version).
• The setting Dash0OperatorConfiguration.spec.kubernetesInfrastructureMetricsCollectionEnabled is deprecated. Please use Dash0OperatorConfiguration.spec.kubernetesInfrastructureMetricsCollection.enabled instead. (The deprecated option still works though, it might be removed in a future version). (Note that the Helm value kubernetesInfrastructureMetricsCollectionEnabled is not affected by this change.

Full Changelog: https://github.com/dash0hq/dash0-operator/compare/0.58.0...0.59.0