Ivan Ka
/kind cleanup
@mloiseleur , @mcharriere wdyt?
Having round-trips and backoff not make much sense, the logic is going to be quite hard to understand. I have no issue to close this pull request. The new format...
Apex support is buggy.... https://github.com/kubernetes-sigs/external-dns/issues/449. I manage APEX in terraform, or have some propriatery code at the moment.
Another option is to only support legacy for apex domain. Dunno. Thix TXT issue needs a proper owner who could: - agree on interface - implement a solution
> For example.com the old format creates a TXT record myprefix.example.com (Success), and the new format will constantly try to create e.g. myprefix.cname-example.com (Failure), which doesn't work as that domain...
So how it currently works for Apex domains? I have not found a flag to disable upsert for new format. Does external-dns errors out, crashes, or swallow the error?
Got it. Will try to find a solution for apex records, before merging this to master /hold
I think the question is, how to reliably `determine if zone apex or subdomain`.......