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
AWS NLB in dual-stack does not create AAAA record #3707
Comments
In our case most traffic goes through
The AWS Load Balancer Controller configures the NLB based on those annotations. I'll dig around and see if I can figure out the golang, but this is all spaghetti to me. This "should" be covered by the |
We see the same thing for a dual stack NLB where the targets (ingerss-nginx) all listen on IPv6:
So NLB <-> ingress-nginx is IPv6 only, but everything uses the NLB with IPv4 since the AAAA record doesn't get created. Deleting the TXT/A record does not help as only they are recreated with the corresponding AAAA alias to the NLB. |
This is a different issue in my opinion. 1877 is about AAAA records not being created if you switch from ipv4-only to dualstack. This is indeed also an issue, but not the one we're seeing. This issue is about using an NLB. There I never manage to let it create AAAA record. Also not if you create a branch new loadbalancer, which works fine with the ALB. |
This will be fixed with #3605 |
OK, that would be cool. Any idea on the timing? |
Things are likely to remain stalled around here until September, when I meet a key requirement for becoming an approver. |
Thx. I should be able to defend that timeline internally. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When creating an AWS Network-load-balancer in dual-stack mode, external-dns does not create a AAAA record in route53. It works perfectly fine in the same setup with an ALB
What happened: Only an A record is created
What you expected to happen: an AAAA record to be created
How to reproduce it (as minimally and precisely as possible):
Deploy the following service:
Anything else we need to know?:
Environment:
external-dns --version
): 0.13.5The text was updated successfully, but these errors were encountered: