We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened:
I have a AAAA alias record. The AWS provider translates the record into an A record.
See: https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L1142 https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L486 https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L779
This results in my A and AAAA aliases with the same name colliding.
What you expected to happen: I expect AAAA records to be treated as AAAA.
How to reproduce it (as minimally and precisely as possible):
I have a CRD with:
spec: endpoints: - dnsName: my.example.com labels: k8slens-edit-resource-version: v1 providerSpecific: - name: aws/evaluate-target-health value: 'true' - name: alias value: 'true' - name: aws/region value: eu-west-2 - name: aws/target-hosted-zone value: ZONEIDHERE recordType: AAAA setIdentifier: myid-1 targets: - myother.example.com
This fails to create heritage record and the alias record.
Anything else we need to know?:
I found this somewhat related PR: #3605
Environment:
external-dns --version
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened:
I have a AAAA alias record. The AWS provider translates the record into an A record.
See:
https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L1142
https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L486
https://github.com/kubernetes-sigs/external-dns/blob/master/provider/aws/aws.go#L779
This results in my A and AAAA aliases with the same name colliding.
What you expected to happen:
I expect AAAA records to be treated as AAAA.
How to reproduce it (as minimally and precisely as possible):
I have a CRD with:
This fails to create heritage record and the alias record.
Anything else we need to know?:
I found this somewhat related PR: #3605
Environment:
external-dns --version
): 0.15.0The text was updated successfully, but these errors were encountered: