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.

Sign up for GitHub

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

Jump to bottom

External-dns pod crash looping on EKS IPV6 clusters when using provider aws-sd #4713

Closed

abrarcv170 opened this issue Aug 30, 2024 · 2 comments · Fixed by #4721

Assignees

Labels

kind/bug

abrarcv170 commented Aug 30, 2024

The external-dns pod is crash looping with the following error message. The provider used is aws-sd.

time="2024-08-28T13:26:29Z" level=fatal msg="Failed to do run once: invalid endpoint type (consul.staging.internal 0 IN AAAA 2a05:XXXX:XX:5300:a8e5::a;2a05:XXXX:XX:5301:e897::d;2a05:XXXX:XX:5302:2c3c::b [])"

Version used : v0.14.2

abrarcv170 added the kind/bug label

Contributor

mjlshen commented Sep 4, 2024

/assign

k8s-ci-robot assigned mjlshen

mjlshen mentioned this issue

Add AWS_INSTANCE_IPV6 support to the AWS-SD provider #4721

Merged

2 tasks

Contributor

mjlshen commented Oct 19, 2024

Hi @abrarcv170 I'm pretty sure, but I'd like to ensure that my PR fixes your issue. Do you have a sample Service or Ingress you were using that I can use to test? If not, that's ok.

k8s-ci-robot closed this as completed in #4721

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment