Allow configuring TXT registry to only generate the "new" format of TXT records

[mjlshen]

What would you like to be added: Currently when using the TXT registry, two TXT records (old + new format) are being created for every record the external-dns creates: https://github.com/kubernetes-sigs/external-dns/blob/c45d0de9090669ee9a40487b6fab7b9b98be7baf/registry/txt.go#L212-L242

I would like to propose a flag (or some other way) to configure the TXT registry to only use the new format.

Why is this needed: I am trying to use external-dns to manage DNS records at scale and am running into cloud provider limits, e.g. by default Azure public DNS Zones allow for a maximum of 10,000 record sets. This quota can be increased, but if external-dns can be configured so that the TXT registry only creates one additional record, this would be a massive improvement for my use-case.

[mloiseleur]

@mjlshen Maybe you will be interested in https://github.com/kubernetes-sigs/external-dns/issues/4575. Using CR as a registry could help overcome this kind of limitations, too.

[maxwell-gregory]

Having 3 records to sync with external-dns and my DNS provider is causing rate limiting. Any hopes on a fix for getting rid of this old txt record style?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale