Skip to content

feat: ExternalDNS - #128

Open
peucastro wants to merge 13 commits into
mainfrom
feat/external-dns
Open

feat: ExternalDNS#128
peucastro wants to merge 13 commits into
mainfrom
feat/external-dns

Conversation

@peucastro

Copy link
Copy Markdown
Member

it works ig

image

TODO

  • Find a better way to handle IngressRoute discovery without the need of setting a specific target
  • Delete the dev/test-external-dns service

@peucastro

Copy link
Copy Markdown
Member Author

According to the documentation, when routing via Traefik IngressRoute, ExternalDNS cannot natively discover the public endpoint. This requires us to manually specify the external-dns.alpha.kubernetes.io/target pointing to the Traefik LoadBalancer external IP for all services.

This is not very convenient, so I'm researching some ways to handle this better. Feel free to edit this comment and add more options

  • Migrate from IngressRoute to standard Kubernetes Ingress resources: Traefik natively populates the .status.loadBalancer field on standard Ingress objects, allowing ExternalDNS to discover the external IP automatically.
  • Deploy traefik-external-dns-controller to automatically populate this value

@FrozenHart FrozenHart linked an issue May 28, 2026 that may be closed by this pull request
@rubuy-74
rubuy-74 self-requested a review May 28, 2026 16:47
@peucastro
peucastro marked this pull request as ready for review May 29, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automate DNS subdomain

3 participants