Cloudflare wildcard entry updates every minute

[jessebye]

What happened:

External-dns is updating a Cloudflare wildcard DNS entry every minute:

time="2020-09-14T20:13:47Z" level=info msg="Changing record." action=UPDATE record="kraken-prod*.advclient.com" ttl=1 type=TXT zone=<redacted>
time="2020-09-14T20:14:45Z" level=info msg="Changing record." action=UPDATE record="*.advclient.com" ttl=1 type=CNAME zone=<redacted>
time="2020-09-14T20:14:46Z" level=info msg="Changing record." action=UPDATE record="kraken-prod*.advclient.com" ttl=1 type=TXT zone=<redacted>
time="2020-09-14T20:15:48Z" level=info msg="Changing record." action=UPDATE record="*.advclient.com" ttl=1 type=CNAME zone=<redacted>
time="2020-09-14T20:15:49Z" level=info msg="Changing record." action=UPDATE record="kraken-prod*.advclient.com" ttl=1 type=TXT zone=<redacted>

What you expected to happen:

The entry should be created once and not updated unless it actually changes.

How to reproduce it (as minimally and precisely as possible):

1. Use the Cloudflare provider per instructions.
2. Add resources that will create a wildcard record.
3. Observe the update loop.

Anything else we need to know?:

Environment:

• External-DNS version (use external-dns --version): 0.7.3
• DNS provider: cloudflare
• Others:
  Relevant config:

Sources: [service ingress istio-gateway istio-virtualservice]
CloudflareProxied: true
CloudflareZonesPerPage: 50

[seanmalloy]

This pull request might be related: #1695

[jessebye]

@seanmalloy yes it does look related! I'll keep an eye on that PR and see if this issue is fixed once it's merged.

[guxlightyear]

Unrelated to this ticket, but does the CloudflareProxied: true work for you on wildcard domains? We'll open a different issue, but we are trying to use external-dns with a wildcard domain, and have it proxied through Cloudflare CDN, and we don't seem to be able to make it work.

[sheerun]

Fix is in master, it should be fixed in v0.7.5 or higher, when released, The issue is probably -1 for ttl of proxied field

/close

[k8s-ci-robot]

@sheerun: Closing this issue.

In response to this:

Fix is in master, it should be fixed in v0.7.5 or higher, when released, The issue is probably -1 for ttl of proxied field

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.