-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
EKS Node Group Resource Tag Inheritance #13643
Comments
@jornj-lululemon Thanks for raising this issue. |
@ewbankkit Thanks for the triage, one thing to note is that the eks_node_group resources expose the autoscaling group name attribute list under |
FYI, Ive asked AWS SA that i work with to ask the EKS service team to address this, its seems to be in their roadmap. |
Please note I'm dual labeling this issue -- if the upstream EKS API implements tag propagation support, great! Otherwise, we can consider the following new resource type for managing Autoscaling tags in the meantime: resource "aws_autoscaling_tag" "example" {
key = "key1"
propagate_at_launch = true
resource_id = aws_eks_node_group.my_resource_name.resources[*].autoscaling_groups[*].name
value = "value1"
} |
This functionality has been released in v3.56.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Community Note
Description
Currently EKS Node Group resources create autoscaling groups that do not inherit or pass down any configuration defined tags except the default EKS service association tags. AWS EKS clusters (both on the cluster itself and created node groups) currently do not support tag propagation, and terraform only appears to track the autoscaling group name(s) created by the EKS node group resource. Since the AWS terraform provisioner does not have functionality to define supplemental tags on untracked resources, the current workaround seems to be creating a local_exec provisioner calling the AWS autoscaling CreateOrUpdateTags API call.
New or Affected Resource(s)
eks_node_group
Potential Terraform Configuration
or
References
https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html
https://docs.aws.amazon.com/autoscaling/ec2/APIReference/API_CreateOrUpdateTags.html
The text was updated successfully, but these errors were encountered: