The dnsPolicy cannot be defined for the DatadogAgent in v2alpha1

[13013SwagR]

Output of the info page (if this is a bug)

None

Describe what happened: The dnsPolicy cannot be defined for the DatadogAgent since v2alpha1.

Describe what you expected: The dnsPolicy to be available as an override in spec.override.[key].dnsPolicy or the dnsPolicy to be set to ClusterFirstWithHostNet when setting spec.override.[key].hostNetwork like it used to be on the HelmChart install

Steps to reproduce the issue: See https://github.com/DataDog/datadog-operator/blob/main/docs/configuration.v2alpha1.md#override

Additional environment details (Operating System, Cloud provider, etc): We have a custom dns setup and we need to set dnsPolicy to ClusterFirstWithHostNet like we currently have with the Agent Helm Chart installation.

[13013SwagR]

Hello @khewonc ,

I urge reconsidering the classification of the missing dnsPolicy in v2alpha1 as a mere feature request. This functionality was present in v1alpha1 and is documented here. Its absence in v2alpha1 is a regression that disrupts established configurations and impacts critical network operations.

Previously, users could set dnsPolicy explicitly or rely on automatic settings tied to hostNetwork. Removing this without a clear alternative affects those of us with custom DNS setups transitioning from Helm or v1alpha1.

Please consider this a bug due to its significant impact on functionality and user experience. Addressing this would help ensure consistency and reliability for configurations across versions.

Thank you for your attention to this matter.

[Eokye]

@13013SwagR Thanks for bringing this to our attention. The issue has been resolved in the 1.8 release.

[13013SwagR]

Thanks, I'll test!