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

Support default_tags in aws_autoscaling_group #1916

Closed
caleb-devops opened this issue Mar 2, 2022 · 6 comments · Fixed by #1973
Closed

Support default_tags in aws_autoscaling_group #1916

caleb-devops opened this issue Mar 2, 2022 · 6 comments · Fixed by #1973

Comments

@caleb-devops
Copy link

Is your request related to a problem? Please describe.

Tags created in the default_tags block in the AWS provider are not applied to aws_autoscaling_group.

Describe the solution you'd like.

Apply default_tags to the aws_autoscaling_group in the self-managed-node-group module.

Additional context

https://learn.hashicorp.com/tutorials/terraform/aws-default-tags?in=terraform/aws#propagate-default-tags-to-auto-scaling-group

@kishore-kumar-ripcord
Copy link

I agree, plus this is needed for EKS managed node group as well without using custom launch template.

@bryantbiggs
Copy link
Member

I agree, plus this is needed for EKS managed node group as well without using custom launch template.

Thats not possible unless AWS supports it in the API

@thecosmicfrog
Copy link

thecosmicfrog commented Mar 24, 2022

@bryantbiggs I'm beginning the migration from v17 to v18 at the moment. I believe I'm right in saying create_launch_template = false is required to support using disk_size = N in eks_managed_node_group_defaults{}, correct?

This works fine, but this first thing I noticed is that tags are no longer propagated to the EC2 instances (so all instances have "blank" names in the console).

So, is the only solution to this is to manage our own launch template? Thanks.

@antonbabenko
Copy link
Member

This issue has been resolved in version 18.16.0 🎉

@stevo-f3
Copy link

stevo-f3 commented Sep 5, 2022

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this issue 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 similar to this, 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 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
6 participants