-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
external-dns is unable to sync AWS records #2793
Comments
We are seeing the same error message external dns v.0.12.0
I believe the "cname-" prefix is causing the batch apply to fail. Anyone has an idea why the "cname-"? Thanks. |
Now it creates/deletes old and new txt owner records - new records are with type eg.cname Lines 152 to 157 in f3e04df
Changes to provider are send in bateches and it looks like AWS refused whole batch when it hits non existing record ( new one with type ). EDIT: batch size is configurable, i would not recommend this in production, but you could pass --aws-batch-change-size=1, this would allow to create and delete records, only delete operation for nonexistent txt owner records (new once with type) will fail. It will work, because failing batch will always contain only 1 record, not all changes as default for batch is 1000. |
We are also seeing these errors. In sync mode.
The zone is used for testing so I went as far as to delete all of the records but the error came back. The issue is not seen on 0.11. Definitely seems to be related to #2157 |
I'm trying to reproduce this |
I got the same error when I delete a resource created by external-dns v0.11.0 with v0.12.0 running. |
Ignoring an error won't help here. I'm working on some sort of init container to perform a cleanup |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This is fixed in v0.12.2 |
Hello, S'ill facing this issue today on AWS. Bumping from an old version to latest (with handle registry on TXT records) causes logs indicating BatchError for the CREATE on We resolved this with #2897 by creating manually the TXT records. Lastly, external-dns succeed to update those. |
Recently I tried migrating service loadbalancer from one cluster to another but when looking the external-dns logs I see below error.
for policy, I got upsert-only.
Please let me know if I'm something here.
The text was updated successfully, but these errors were encountered: