Instrument pods instead of workloads with the Dash0 operator
The operator can now instrument pods at creation and leave your deployments untouched.
Starting with version 0.160.0, the Dash0 operator can instrument pods when they are created, instead of modifying the pod templates of deployments, stateful sets and other workloads.
To switch a namespace over, set spec.instrumentWorkloads.mode: pods in its Dash0 monitoring resource. Since the workload resources are never modified, tools like Argo CD, Flux or Terraform no longer see drift caused by the operator. Pods created by other controllers, for example Argo Rollouts, are instrumented as well.
The operator doesn't restart pods to instrument them: existing pods pick up the instrumentation the next time they are recreated. The mode is set per namespace, so you can switch namespaces one at a time. We recommend running two operator replicas (operator.replicaCount=2) so that the webhook stays available during operator updates.
For details, see the documentation.