Sebastian

this is great to hear @ytsarev! I'll see if I can grab some time (and refresh my memory first :D) I would also make the switch to Workload Identity if...

> @sebader, thanks a lot for this work! Could you please squash the commits? done

> PR looks good, can you add information to the docs that NS records will not work if the `managed-record-type` is not configured to also use NS records? sorry, @Raffo...

ah got it @Raffo. I added a note to the docs, is that ok? Yes, I have tested the new NS records through k8gb - I guess there the managed-record-types...

> @sebader Sebastian Bader FTE Do you think you can rebase this PR ? puh... I haven't touched this in ages and not even a working local setup for this...

I landed here as well with the same issue. We are using kube_dashboard and hence have the omsagent Identity assigned to the nodes as well. Thus we cannot use cert-manager...

Actually, there is an open PR for this :) https://github.com/jetstack/cert-manager/pull/4332

My long-open PR which adds NS support for Azure, would need to completely rebuild after this is merged. How about integrating NS support into this PR directly? https://github.com/kubernetes-sigs/external-dns/pull/2835

/reopen this has on open PR assigned https://github.com/kubernetes-sigs/external-dns/pull/2835

/reopen