DataDog
Operator does not honor DD_SITE
in values.yaml of the operator chart, it reads:
# site -- The site of the Datadog intake to send data to (documentation: https://docs.datadoghq.com/getting_started/site/)
## Set to 'datadoghq.com' to send data to the US1 site (default).
## Set to 'datadoghq.eu' to send data to the EU site.
## Set to 'us3.datadoghq.com' to send data to the US3 site.
## Set to 'us5.datadoghq.com' to send data to the US5 site.
## Set to 'ddog-gov.com' to send data to the US1-FED site.
site: # datadoghq.com
# dd_url -- The host of the Datadog intake server to send Agent data to, only set this option if you need the Agent to send data to a custom URL
## Overrides the site setting defined in "site".
dd_url: # <DATADOG_API_ENDPOINT>
I was setting site: datadoghq.eu, and expected the operator to use the EU endpoint. That's not the case. It uses the default US endpoint - at least for monitors so I ended up with 403.
The docs right above dd_url was confusing me even more, so I did not use that when in fact - after reading through the sources, it was solving me issue.
I think operator should use site in context of monitor and potentially other custom resources as well.
Hi @deas , thanks for reporting. You are correct and we will update this issue when it is fixed.
As a workaround for now, setting DD_URL = https://api.datadoghq.eu should work.
Hello i got the same issue too, the code has not been updated https://github.com/DataDog/datadog-operator/blob/7c39c354538672d56342d612c1fe1a7279502ff9/pkg/datadogclient/client.go#L47 it only takes into account DD_URL @celenechang any plans to fix it ? :)
also ran into this issue. Datadog support linked me directly to this ticket so I guess they're aware of it. hopefully it can be fixed soon....
Hi everyone, apologies for the delay in addressing this - I somehow missed the recent notifications. We'll prioritize this ASAP.
This was fixed in https://github.com/DataDog/datadog-operator/pull/838 and will be part of operator 1.1.0 . Thanks for your patience.