Cloudflare provider can't handle multiple records.

[kevincox]

The cloudflare providor misbehaves if a service has multiple external IP addresses. For example if you have a single existing (managed) records it will replace the record with the other each iteration.

1 existing 2 current case.

1.You have an ingress with external IPs 1.1.1.1 and 2.2.2.2.

1. 1.1.1.1 is an A record in cloudflare.
2. external-dns notices you already have 1.1.1.1 and tries to update the record to have 2.2.2.2.
3. The 1.1.1.1 record gets replaced with 2.2.2.2.
4. You now have only 2.2.2.2 in cloudflare.
5. external-dns noticies you have 2.2.2.2 in cloudflare and tries to update the record to have 1.1.1.1.
6. Go back to step 2.

You will have correct IPs now, but only one at a time.

2 existing 2 current case.

1.You have an ingress with external IPs 1.1.1.1 and 2.2.2.2.

1. 1.1.1.1, and 9.9.9.9 are A records in cloudflare.
2. external-dns notices you already have 1.1.1.1 and tries to update the record to have 2.2.2.2 and remove 9.9.9.9
3. The 1.1.1.1 record gets replaced with 2.2.2.2, 9.9.9.9 is untouched.
4. external-dns notices you already have 2.2.2.2 and tries to update the record to have 1.1.1.1 and remove 9.9.9.9
5. The 2.2.2.2 record gets replaced with 1.1.1.1, 9.9.9.9 is untouched.
6. Go back to step 2.

This case is worse, you always have one correct IP, but the incorrect IP never gets removed.

Note: I haven't tested other providers so it might be a wider problem.

cc: @njuettner

[ideahitme]

I don't think problem is specific to cloudflare and probably applicable to all cloud providers (the error is caused by erroneous internal external-dns logic). External DNS does not support multiple targets (i.e. case when one service/ingress generates more than one endpoint) and hence the problem. Related PRs and issues: #243, #270)

However, this problem can be caused also by creating two ingresses/services requesting same DNS name, as addressed and described here: #261, #258

I am closing this as this is a duplication, please comment if u disagree

[cusspvz]

This shouldn't be closed since support for multiple targets was added but we still don't have support for multiple records handling/set on cloudflare.

We're only setting the first item of the target's array: https://github.com/kubernetes-incubator/external-dns/blob/74de102a130018052dc6551955fd1c12b0e1fc84/provider/cloudflare.go#L299

[cusspvz]

@ideahitme can you please reopen this?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.