Add support for external-dns to Emissary v2
See original GitHub issueWe use external-dns to manage the DNS entries for our Hosts, which works beautifully in the v1.x series of Emissary. There appears to not be this support in v2.x, meaning we can’t upgrade to v2. 😱
Please add support for external-dns to v2 of Emissary, in the Host
object as per v1 would be ideal.
v1 does this via the external-dns.ambassador-service
annotation on the Host
object
Relates to https://github.com/emissary-ingress/emissary/issues/1057 somewhat, I guess?
Some mention of this support in the docs would be good too - even a search on the v1 docs site brings no results… you need to deep dive (into code, or the Slack community) to even know about it at all… 😓
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Add support (might just be docs) for external DNS · Issue #1057
I can't tell from the docs if it's possible, easy, or impossible. On aws, we usually just add the annotation (to a service)...
Read more >ExternalDNS with Emissary-ingress | Ambassador
ExternalDNS with Emissary-ingress ExternalDNS configures your existing DNS provider to make Kubernetes resources discoverable via public DNS servers by…
Read more >external-dns - Bitnami - Artifact Hub
Name Description Value
image.registry ExternalDNS image registry docker.io
image.repository ExternalDNS image repository bitnami/external‑dns
image.pullPolicy ExternalDNS image pull policy IfNotPresent
Read more >Installing the Emissary ingress with the Linkerd service mesh
Once your mesh is up and running, you can integrate it with Emissary. To do this, you must add the ambassador ingress itself....
Read more >Emissary-ingress 2.2.2: How to enable https on kubernetes ...
... "kubernetes-dashboard-dns" # namespace: "kubernetes-dashboard" annotations: external-dns.ambassador-service: emissary-ingress.emissary ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Support for ExternalDNS is documented at https://www.getambassador.io/docs/emissary/latest/howtos/external-dns/.
Looking at the https://github.com/kubernetes-sigs/external-dns/blob/master/source/ambassador_host.go it seems that it should work with Emissary because
getambassador.io/v2
API version andHost
kind lines up. It seems that it’s necessary to addexternal-dns.ambassador-service=emissary-ingress/emissary
annotation to everyHost
thatexternal-dns
should manage (assuming default Emissary LB service location). Do I get this right @egeland?@kflynn maybe you can share what you needed to do to get
external-dns
working with Emissary Ingress 2.1?