Skip to content
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

feat: Match block_device_mappings with workers_launch_template in node group #1721

Conversation

kongdewen
Copy link
Contributor

Description

In https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers_launch_template.tf, the module support root_block_device_name as variable, and also added support for additional_ebs_volumes and additional_instance_store_volumes, It will be nice if we can match the same flexibility as we support node groups as now we are supporting custom AMI image.

Motivation and Context

It starts with issue fix: #1714. Thought why don't we want to do more

Breaking Changes

N/A

How Has This Been Tested?

We have a batch version fixed the issue(#1714) deployed in our prod account.
for additional_ebs_volumes, additional_instance_store_volumes, we don't have any usage yet, we only did terraform plan for test scenario.

@kongdewen kongdewen changed the title improvement: match block_device_mappings with workers_launch_template in node group feat: match block_device_mappings with workers_launch_template in node group Dec 17, 2021
@kongdewen kongdewen changed the title feat: match block_device_mappings with workers_launch_template in node group feat: Match block_device_mappings with workers_launch_template in node group Dec 17, 2021
@antonbabenko
Copy link
Member

This issue has been resolved in version 18.0.0 🎉

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants