Override defaultTXTRecordPrefix in ExternalDNS about external-dns-operator HOT 5 CLOSED

Hello @alebedev87,

we have different OpenShift Clusters running and want to use the External DNS Operator on all of them using the same Hosted Zone in AWS. The problem we're facing is, that the operator from the frist cluster is deleting the records created by the second operator because we can't customize the defaultTXTRecordPrefix` = "external-dns-" configuration.

from external-dns-operator.

Hello @Aldjinn,

No, it's not possible to provide TXT prefix via the API. The prefix is added to avoid the conflict of TXT and CNAME records. The whole existence of the TXT records and their prefix is more of a technical detail for how to find out which records belong to this instance of ExtDNS.

Any concrete use case why you would like the prefix to be different?

from external-dns-operator.

@FlorianHoehner: Indeed, there can be the ownership conflict if there are 2 external-dns managed by this operator which use the same hosted zone. But only in case these 2 ExternalDNS CRs (no matter the cluster) have the same name. The name of the CR is used as the owner ID for the TXT records.
So, if I understand the problem correctly, it would be enough to just prefix/suffix the CR names with the corresponding cluster IDs. This will result in TXT records with different owner IDs and the external-dns instance won't be touching the other cluster's TXT records anymore.

from external-dns-operator.

We will give it a try. Thx. 👍🏻

from external-dns-operator.

Using different names for ExternalDNS on all clusters works great.
Thx @alebedev87 for the quick help.

🐱‍👓

from external-dns-operator.