DWSR
DWSR

Reputation: 631

Getting External-DNS to work with Ingress Objects in Kops AWS 1.7 K8s Cluster

I'm trying to figure out how to get this setup to work:

In this scenario, cert-manager is reacting appropriately to the Ingress object (modifying it to complete the ACME challenge), but external-dns is not doing anything (logs are saying all hostnames are up to date). If I manually add a Route53 record for the ELB associated with the LB service, everything works as expected. Inspecting the Ingress object, I see that the status block looks like so:

status:
  loadBalancer:
    ingress:
    - {}

which I suppose is why external-dns isn't reacting? How do I get this to work? Per the documentation

More troubleshooting information (pod definitions, ingress definitions, controller logs, etc.) can be found here: https://gist.github.com/DWSR/f6d596850346223393bec23b289c9731

Upvotes: 2

Views: 1245

Answers (1)

DWSR
DWSR

Reputation: 631

I solved this myself. The nginx ingress controller has a --publish-service command line argument which will cause it to update the status fields on the ingress objects which, in turn, will cause external-dns to create the appropriate DNS records. When installing via Helm, simply set .Values.controller.publishService.enabled to true and this will take effect.

Sources:

Upvotes: 3

Related Questions