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

Enable Network Load Balancer (NLB) dualstack #883

Merged
merged 1 commit into from
Nov 21, 2020
Merged

Conversation

dghubble
Copy link
Member

  • NLB subnets assigned both IPv4 and IPv6 addresses
  • NLB DNS name has both A and AAAA records
  • NLB to target node traffic is IPv4 (no change), no change to security groups needed
  • Ingresses exposed through the recommended Nginx Ingress Controller addon will be accessible via
    IPv4 or IPv6. No change is needed to the app's CNAME to NLB record

Related:

* NLB subnets assigned both IPv4 and IPv6 addresses
* NLB DNS name has both A and AAAA records
* NLB to target node traffic is IPv4 (no change),
no change to security groups needed
* Ingresses exposed through the recommended Nginx
Ingress Controller addon will be accessible via
IPv4 or IPv6. No change is needed to the app's
CNAME to NLB record

Related: https://aws.amazon.com/about-aws/whats-new/2020/11/network-load-balancer-supports-ipv6/
@dghubble dghubble merged commit 5e4f5de into master Nov 21, 2020
@dghubble dghubble deleted the aws-ipv6-ingress branch November 25, 2020 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant