levan-m

Hello, sorry for not getting to the issue on time. Operator `v0.x` is no longer supported and we recommend migrating to most recent version of `v1.x`. Please open a new...

Hello, sorry this issue didn't get any attention so far! The original issue refers to Operator 0.8.6 beta version. We made Operator 1.0 generally available in April and at this...

Overall LGTM (haven't reviewed doc); left few comments which may require small changes.

This config was added to admission controller feature in Operator 1.7.0 under `features.admissionController.registry`.

Sorry we weren't able to get to this issue so far. In order to investigate this further, can you please open a support ticket via [Datadog Help](https://docs.datadoghq.com/help/), referencing this github...

Thanks for the reporting the issue @paulbrassard-figure! As mentioned [here](https://github.com/DataDog/datadog-operator/pull/1177#issuecomment-2130151444) the fix addressed once specific case leading to duplication - namely concurrent reconciliation of the resource. With SLO Create API...

@JCMais thanks for providing the configuration for `v2alpha1`! Since `v1alpha1` is deprecated I'm closing the issue.

Hello, Thanks for submitting the issue! You are right `0.8.x` managed PDB for both Cluster Agent and Cluster Checks Runners, this isn't yet supported in `1.x.x`, fact highlighted [here](https://github.com/DataDog/datadog-operator#migrating-from-08x-to-100). We...

This was resolved in 1.1.0.

Closing the issue as it was originally opened for DatadogAgent `v1alpha1` version which is now deprecated.