Added callout for DNS64 with EKS IPv6 support #712
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes: This change calls out that DNS64 should be disabled on the subnets in order to get the desired behavior depicted in the Pod to an external IPv4 endpoint pattern . DNS64 is only needed on the subnets if you are running IPv6 only workloads in the subnet that need to communicate to IPv4 endpoints. Since the CNI plugin is installed (and recommended) on the EKS cluster, the pods have both an IPv4 and IPv6 address. Thus, when DNS64 is enabled on the subnet and a pod is looking to communicate with an only IPv4 endpoint (like a DynamoDB Gateway endpoint) a synthesized IPv6 address is returning thus causing the pod to use the IPv6 address (since it prefers it) which then causes the traffic to go to the NAT Gateway to do the NAT64 translation. This flow through the NAT Gateway, while it works, will unnecessarily drive up NAT Gateway usage.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.