external-dns: DNS not updated when load balancer changes address

What happened: Contour logs

time="2021-09-20T17:37:52Z" level=info msg="received a new address for status.loadBalancer" context=loadBalancerStatusWriter loadbalancer-address=a09eed6b7d4769a328a1dc38396843-b3258fd74268025a.elb.us-east-1.amazonaws.com

external-dns logs:

time="2021-09-21T16:51:58Z" level=info msg="All records are already up to date"

Envoy service data:

AME    TYPE           CLUSTER-IP       EXTERNAL-IP                                                                     PORT(S)                      AGE   SELECTOR
envoy   LoadBalancer   10.100.146.240   a09eed6b7d4769a328a1dc38396843-b3258fd74268025a.elb.us-east-1.amazonaws.com   80:31483/TCP,443:32088/TCP   23h   app=envoy

What you expected to happen: Update of the new CNAME in Route53 Essentially that’s the only thing I expect of external-dns nothing else.

How to reproduce it (as minimally and precisely as possible): Use external-dns with projectcontour on EKS

About this issue

Original URL
State: open
Created 3 years ago
Reactions: 7
Comments: 20 (2 by maintainers)

Most upvoted comments

Reproduced again, and again, and again. It seems like external-dns just doesn’t really handle load balancer address change at all. I.e. the one and only functionality it’s needed for

pkit on Dec 2, 2021

@k0da added --events but did not help. Updated ingress class to new one and 30 min passed. external-dns did not update route 53 yet. external-dns pod arguments:

--log-level=info --log-format=text --interval=1m --events --source=service --source=ingress --policy=upsert-only --registry=txt --provider=aws

ismailyenigul on Nov 14, 2022