How to **not** install the DNSEndpoint CRD twice when using the Helm chart twice (for 2 different providers) on the same namespace ?

[davidandreoletti]

The core issue is in the question. I have not identified any property in values.yaml to disable DNSEndpoint and the DNSEndpoint is not guarded with anything to conditionally generate it.

[ivankatliarchuk]

Has nothing with external-dns project. Helm docs should help

[davidandreoletti]

@ivankatliarchuk I would like to disable installing the external-dns's DNSEndpoint CRD deployed as part of the external-dns's Helm chart.

However, the Helm chart's values.yaml provides no option not to install this CRD unlike cert-manager's Helm Chart crd.install property for instance.

I would prefer not to rely on Helm directly even if possible via its installCRDs option.

Do we now have the same understanding ?

[ivankatliarchuk]

No we not on the same page. Please read the Helm docs, this has nothing with external-dns, make yourself familiar with the tool you are using. https://helm.sh/docs/helm/helm_install/

[ivankatliarchuk]

I'm not a Helm maintainer for this project. If you're using Helm, please use the standard Helm commands and features. If an off-the-shelf chart has limitations that block your use case, consider forking the chart. We can't add custom Helm functionality here - you could create an Issue and try to convince helm maintainers that this feature is required.

For context, there have been past attempts to add similar features: https://github.com/kubernetes-sigs/external-dns/pulls?q=is%3Apr+helm+disable+crd+is%3Aclosed+

I don't believe this feature is necessary. Helm already supports skipping CRD installation via --skip-crds. CRD management within Helm has known limitations, and supporting additional workarounds is just does not sound correct from maintenance perspective.