-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Adding support for launch templates & userdata parameters #27
Adding support for launch templates & userdata parameters #27
Conversation
/test all |
/rebuild-readme |
…form-aws-eks-node-group into add-launch-template-support
/test all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly some questions, but looks great
I still need to port over the logic from |
- Bumping project to TF 13 so that we can use variable validation - Adding dynamic userdata template
/test all |
/test all |
/test all |
This will require TF 0.13 right? |
Yep yep.. we had a discussion about it and the preference was to go w/ 0.13 and use the new validation functionality basically. |
This is looking awesome @danjbh! Went down the rabbit hole of trying to figure why my node-group instances didn't have |
/test all |
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
Co-authored-by: Nuru <Nuru@users.noreply.github.com>
/test all |
what
instance_types
as a list but adding TF 0.13 variable validationwhy
In previous version of the AWS provider (2.x), you could not define your own launch template for
aws_eks_node_group
. Additionally, the tags specified in theaws_eks_node_group
definition were not being passed down to the EC2 instances created by the ASG, which made tasks like monitoring and cost tracking difficult.The latest versions of the AWS provider (3.x) give us the ability to specify our own launch template directly from
aws_eks_node_group
, which allows us to set our own options (e.g.tag_specifications
.user_data
, etc.).This also should satisfy the requests in #24
references