fix: Update EKS module to support AL2023 bootstrapping #689
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.
What does this PR do?
This PR updates the EKS terraform module to bring in support for NodeADM bootstrapping.
it also updates the IAM configuration for Karpenter to use
access_entries
instead ofaws_auth_roles
.Motivation
#688 added MNG using AL2023 AMIs which require newer Bootstrapping:
This
cloudinit_pre_nodeadm
property isn't supported in version 19.x of the EKS terraform module, and the aws_auth entries we use are removed in 20.x+More
website/docs
orwebsite/blog
section for this featurepre-commit run -a
with this PR. Link for installing pre-commit locallyFor Moderators
Additional Notes
I was able to check the ephemeral storage thats being returned from the
spark_benchmark_ssd
1756689344Ki == 1675.3Gi which matches the NVMe space
checking the volumes on the node and it looks like the RAID was setup correctly