Open
Description
When a DatadogMonitor CR is created, it creates a corresponding monitor in Datadog.
When a DatadogMonitor CR is deleted, it deletes the corresponding monitor in Datadog.
When a monitor is deleted in Datadog, the DatadogMonitor CR remains in the cluster and the Datadog Operator pod shows the error:
{"level":"ERROR","ts":"2025-06-08T14:14:01.011Z","logger":"controllers.DatadogMonitor","msg":"error updating monitor","datadogmonitor":{"name":"pod-imagepullbackoff","namespace":"monitoring"},"Monitor ID":174457872,"error":"error updating monitor: 404 Not Found: {\"errors\":[\"Monitor not found\"]}"}
This does not create a consitent experience for Kubernetes being the source of truth. Instead, since the DatadogMonitor still exists in the cluster, I expect the monitor to be recreated in Datadog
Metadata
Metadata
Assignees
Labels
No labels