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

Support for ca-west-1 (Calgary) #4442

Closed
jeremy-albuixech opened this issue May 7, 2024 · 0 comments · Fixed by #4444
Closed

Support for ca-west-1 (Calgary) #4442

jeremy-albuixech opened this issue May 7, 2024 · 0 comments · Fixed by #4444
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@jeremy-albuixech
Copy link
Contributor

What happened:
We are trying to deploy a cluster in the new Canadian AWS region, ca-west-1 (Calgary).
Our external-dns pods are failing with the following errors (trimmed):

time="2024-05-07T17:48:33Z" level=warning msg="Could not find canonical hosted zone for domain [...].elb.ca-west-1.amazonaws.com. This may be because your region is not supported yet."
[....]
time="2024-05-07T17:48:34Z" level=error msg="Failed submitting change (error: InvalidChangeBatch: [RRSet of type CNAME with DNS name <redacted>. is not permitted at apex in zone <redacted>.]\n\tstatus code: 400, request id: [...]), it will be retried in a separate change batch in the next iteration"

What you expected to happen:
This should work and let us create records in that region.

How to reproduce it (as minimally and precisely as possible):
Try and use external-dns to create an ELB in that region.

Anything else we need to know?:

Environment:

  • External-DNS version (use external-dns --version): v0.13.6
  • DNS provider: Route53
  • Others:
@jeremy-albuixech jeremy-albuixech added the kind/bug Categorizes issue or PR as related to a bug. label May 7, 2024
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