Ivan Ka
The issue with TXT record not created for apex record, is described here https://github.com/kubernetes-sigs/external-dns/issues/5924. Historically, external-dns is not able to reliably manage apex domains/records with certain providers/registries.
Host and targets could not be the same. Think off `external-dns.alpha.kubernetes.io/target` should be actual NLBs DNS. Something like ``` apiVersion: traefik.io/v1alpha1 kind: IngressRoute metadata: name: whoami annotations: kubernetes.io/ingress.class: traefik-internal external-dns.alpha.kubernetes.io/target:...
@mloiseleur I bet you know what is happening with Traefik ;-)
/ok-to-test
Share kubernetes manifests, provider and all arguments (not a helm)
To be honest, I'm not sure what this change is intend to improve. Do you have any kubernetes manifests to try out before/with-the-fix?
Potentially resolves or helps to resolve or simply relates - https://github.com/kubernetes-sigs/external-dns/issues/4720 - https://github.com/kubernetes-sigs/external-dns/issues/449 - https://github.com/kubernetes-sigs/external-dns/issues/3977 - https://github.com/kubernetes-sigs/external-dns/issues/4234 - https://github.com/kubernetes-sigs/external-dns/issues/3787
I only performed high-level smoke testing, and the PR behaves as expected. I’m not entirely confident about the apex record check—it doesn’t seem very reliable, and I’m not sure what...