feat: Pass the primary_ipv6
argument to the AWS provider.
#3098
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.
Description, motivation, context
The 5.58.0 release of the Terraform AWS Provider now exposes the
PrimaryIpv6
launch template network interfaces parameter via this PR. This parameter causes the first globally-unique IPv6 address to become the primary IPv6 address of instances launched using the template. This is necessary for dual-stack EKS clusters, where the ingress controller's IPv6 address needs to propagate to the ALB during target registration.The current PR adds the
primary_ipv6
flag when used as follows:Breaking Changes
None.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestI am currently using the
examples/eks-managed-node-group/eks-bottlerocket.tf
in conjunction with the supplied changes (and additional modifications) in a production environment.