-
|
Hi guys, I'm using external-dns for some time now and was wondering if anyone's using it for managing the internal + public zone, like described here:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Hi @mattpopa, I'm using exactly this approach, and what I'm doing is creating 2 deployments, where for 1 I make the settings for the internal zone and in the other I make the settings for the external zone. Perhaps my difference is that I filter through the annotations, as 1 of them looks at 'ingress-class: nginx' and another looks at 'ingress-class: nginx-external', thus putting private IPs in the internal zone and public IPs in the outer zone. But, if I understand correctly and you want to create records equally in both zones, I think you don't need the filter. |
Beta Was this translation helpful? Give feedback.
-
|
interesting idea, thanks for sharing :) How did you filter through annotations? I use the same ingress-class, but the difference would be under its ingress config annotation, like |
Beta Was this translation helpful? Give feedback.
-
|
I followed this guidance here and it worked quite well for me: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/faq.md#running-an-internal-and-external-dns- service I believe that in the case you said, it could be the filter: |
Beta Was this translation helpful? Give feedback.
-
|
excellent, thank you 👍 |
Beta Was this translation helpful? Give feedback.
Hi @mattpopa, I'm using exactly this approach, and what I'm doing is creating 2 deployments, where for 1 I make the settings for the internal zone and in the other I make the settings for the external zone.
Perhaps my difference is that I filter through the annotations, as 1 of them looks at 'ingress-class: nginx' and another looks at 'ingress-class: nginx-external', thus putting private IPs in the internal zone and public IPs in the outer zone.
But, if I understand correctly and you want to create records equally in both zones, I think you don't need the filter.