Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Records that are distinct (two different types) are treated as duplicate endpoints. #4888

Open
jtszalay opened this issue Nov 20, 2024 · 0 comments · May be fixed by #4889
Open

Records that are distinct (two different types) are treated as duplicate endpoints. #4888

jtszalay opened this issue Nov 20, 2024 · 0 comments · May be fixed by #4889
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jtszalay
Copy link

What happened:

I created two records with the same name, same target, same attributes but different record type and saw "Removing duplicate endpoint" logs:

Removing duplicate endpoint my.example.com 0 IN AAAA us my.dev-example.com [{aws/evaluate-target-health true} {alias true} {aws/region us-west-1}]

Where I specify the two endpoints:

 my.example.com 0 IN A us my.dev-example.com [{aws/evaluate-target-health true} {alias true} {aws/region us-west-1}]
 my.example.com 0 IN AAAA us my.dev-example.com [{aws/evaluate-target-health true} {alias true} {aws/region us-west-1}]

What you expected to happen:

I expect both records to be created.

How to reproduce it (as minimally and precisely as possible):
Create two records with same:
Name, Targets, Set ID

Anything else we need to know?:

https://github.com/kubernetes-sigs/external-dns/blob/master/source/dedupsource.go#L48

This is the name check.

Environment:

  • External-DNS version (use external-dns --version): 1.15.0
  • DNS provider: aws
  • Others:
@jtszalay jtszalay added the kind/bug Categorizes issue or PR as related to a bug. label Nov 20, 2024
jtszalay added a commit to jtszalay/external-dns that referenced this issue Nov 20, 2024
@jtszalay jtszalay linked a pull request Nov 20, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant