Description
We also looking to migrate TF to CRD but we have thousands of monitors per cluster, a dozen clusters. What happens to the DD API at this point?
Whats the point on knowing the monitor status wether is Triggered or not? Is not that you will make "alerts" or "monitors" out of this.. in fact, im not sure wether you can even make alerts out of the status field of a CRD in a cluster with datadog at all..
The operator is handy, a good idea.. but seems over-engineered with behaviours like this, if you were in need to receive this status update.. u should consider integrations/webhooks or communication between the DD agent and the operator.
Can we get some flag to turn off this unnecessary overhead ? In theory projecting the creation, deletion and modification of the CRD into the monitor should be enough from a controller perspective.