fix: Add primary_ipv6
parameter to self-managed-node-group
#3169
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
The launch template config in self-managed-node-group didn't include the parameter to set
primary_ipv6
, so I add it here. This has already been implemented for eks-managed-node-group in this PRMotivation and Context
This parameter is needed to enable
Assign primary IPv6 IP
for self-managed-node-group nodes. This is required to make it possible to use instance-type targets when using IPv6 and AWS Load Balancer ControllerBreaking Changes
Simple addition, no breaking changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request