Vincent Boulineau

Hello @edvinas31, It's probably because new Agent version auto detected Docker setup and started using it as a hostname provider. Normally it means you were not using Docker integration before,...

I understood the issue, I'll ship a fix with `7.31.0`.

Yes, was fixed by https://github.com/DataDog/datadog-agent/pull/8949

Hello @cforce, It normally means that no data is available for `avg:kubernetes.cpu.usage{app:myapp,release:myapp}.rollup(30)"`, you can put this query in a Notebook to visualize the data used for autoscaling. If you'd like...

That's the expected behaviour indeed. About `avg:kubernetes.cpu.usage{}.rollup(30)`, querying without any tag is `avg:kubernetes.cpu.usage{*}.rollup(30)`. About checking available tags, you have 2 tools in Datadog to explore metrics/tags: - Metrics explorer -...

Hello @tegioz, We've recently migrated to Operator SDK 1.0 and we're now generating the Docker bundle instead of the folder structure used in community-operators. Is there a plan to support...

Hey @Juandavi1, Currently this is indeed not implemented in the Operator but it's already in our plan!

Hello @lattwood, I've tested the PR and with some minor changes it works fine for checks, and as noted by Dustin, deleting some logs configs may not work (will reword...

> Would it be possible to add tests for this? We don't need to add tests for two reasons: - Being a polling or non-polling provider is not specific to...

@vickenty I've added a test that validates the interaction with `Config` but we cannot really test the registration part. @djmitche I've change the `NOTICE` into `WARNING` about logs config. I...