[service] [request]: eks manage/unmanage nodegroup tags doesn't get propagated to resources (ec2/ebs)

[teochenglim]

Tell us about your request We try to do our AWS costing with AWS tag, however eks manage nodegroup doesn't get the tag propagated from launchtemplate When launch eks new nodegroup, the EC2 instance and EBS volume shall get proper tagging from launchtemplate or equivalence. Without this our costing estimation are all wrong. Without this our monitoring can't base on AWS tag.

Which service(s) is this request for? EKS nodegroup

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? We need to solve our costing problem and monitoring problem with basic AWS tag like all other resources.

Are you currently working around this issue? Manually tagging it. it is time consuming and may paste it (human error) wrong tag and all downstream are all wrong.

Additional context This should be a day 1 feature, don't you think?

Attachments Found out this from AWS support, https://docs.aws.amazon.com/eks/latest/userguide/eks-using-tags.html#tag-resources

[grossdaniel85]

This would be very useful for our use case, too. Apart of the cost estimation described by @teochenglim, we have some cron jobs, which stop EC2 instances over night to save costs. Theses are based on tags of the instance. Naturally, I would like to exclude the nodes from starting and stopping, and therefore need to tag the corresponding instances accordingly. There are workarounds of course, but these are not very convenient.

[migueleliasweb]

I also have another usecase for this. In my usecase, managed node groups don't seem to propagate correctly tags set to them to the underlying ASGs. This prevents some integrations to fully work as the ASGs don't have the proper tags to be atuodiscovered. This is specially bad when using cluster autoscaler.

[ThiyaguE]

I've another usecase; I've tag based cost optimisation and governance controls; I use launchtemplate versions to update/upgrade eks nodegroup. As updated tags keys, mentioned in new launchtemplate version is not propagating to ASG, instances are being created with obsolete tag key/values.. manual tagging is not an option for me. As EKS controls nodegroup ASG and its launchtemplate, aws has to do something here.