-
|
Hi, I'm using external dns and cert manager (with HTTP01 challenge). When I set external dns's policy to sync the DNS records are deleted once the HTTP01 challenge ingress from cert manager is removed. This is against what I would expect since there is still an ingress (the one that uses cert manager to issue the certificate) in the system with the dns name. I know I can use the upsert-only policy, but is there another way to keep that dns record with the policy set to sync? I looked around but couldn't find an anwser. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Answering my own question: the error was on my side. The ingress I tested with did not have ingressClassName specified and there was no default ingress class set up. So the ingress controller actually never picked up the ingress, there was no IP assigned and external dns didn't actually have anything to do - so all works correctly when you do it the right way |
Beta Was this translation helpful? Give feedback.
-
|
@uwej711 Hi. Playing around external-dns in k3s cluster. Works nicely except one thing - |
Beta Was this translation helpful? Give feedback.
-
|
As far as I understand with policy "sync" the records should be deleted once the ingress is deleted. But I don't know how pi-hole and the external-dns implementation for pi-hole works. There could be several places where this breaks. |
Beta Was this translation helpful? Give feedback.
Answering my own question: the error was on my side. The ingress I tested with did not have ingressClassName specified and there was no default ingress class set up. So the ingress controller actually never picked up the ingress, there was no IP assigned and external dns didn't actually have anything to do - so all works correctly when you do it the right way