-
Notifications
You must be signed in to change notification settings - Fork 206
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
ExternalDNS: TXT record issue #715
Comments
This seems to solve the issue kubernetes-sigs/external-dns#262 Is it possible to pass the args in CDK code? |
You can surely pass txtPrefix in the values for the add-on. E.g.
The list of values to pass to the external DNS add-on as extra helm parameters is here. Please let me know if it works. If there is something we need to include in the framework ootb, happy to discuss/include the change. |
@shapirov103 Thanks! I think it could be a great idea to add a default value for txtPrefix as without it it doesn't work properly on route53. |
@shapirov103 I did that in my CDK code but the value is not applied, any thoughts? new blueprints.addons.ExternalDnsAddOn({
hostedZoneResources: [blueprints.GlobalResources.HostedZone],
values:{
'txt-prefix':'xdnstest-'
}
}), |
@cyril94440 it is a bit unclear why you used |
@shapirov103 right? Why would I do that.. sorry stupid mistake, it works fine now! We can either leave this open to force AWS route53 users to add a txtPrefix, or update the documentation or... close it if you feel like it is the responsibility of the user |
Closing this issue. |
Describe the bug
While using ExternalDNS with EKS-Blueprint, the records are created successfully during the first iteration. However, during the second iteration, most of the records are deleted and ExternalDNS gets stuck, throwing an
InvalidChangeBatch
error. This is observed in the logs.Expected Behavior
ExternalDNS should maintain all the DNS records across multiple iterations without deleting them unnecessarily. In this case, we expect that the six DNS records created during the first iteration remain intact during the second iteration and beyond.
Current Behavior
After the first iteration, six DNS records are created successfully. However, during the second iteration, ExternalDNS attempts to create the same records again, resulting in an
InvalidChangeBatch
error due to duplication. Subsequently, all records except two (cname-k8s.acme.ai
andcname-nginx.k8s.acme.ai
) are deleted.Please find the logs below:
First iteration ExternalDNS logs:
Records Created:
Second iteration ExternalDNS logs:
Records REMAINING:
Reproduction Steps
InvalidChangeBatch
error and the deletion of most records.Here is my Ingress manifest:
and CDK code:
Possible Solution
There might be a conflict somewhere as some TXT records are created with and without prefix for a same url...
Additional Information/Context
No response
CDK CLI Version
2.81.0 (build bd920f2)
EKS Blueprints Version
1.8.1
Node.js Version
v18.14.0
Environment details (OS name and version, etc.)
Mac OS 13.2 (22D49)
Other information
No response
The text was updated successfully, but these errors were encountered: