Containers-roadmap: [EKS] [Node Group]: Give EC2 instances a Name tag

[tobdub]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
Add Name tag to EKS nodegroup instances, based on the node group name.

Which service(s) is this request for?
EKS node groups.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Give EKS EC2 node group instances a Name to make them easier to identify, similar to ECS instances.

Are you currently working around this issue?
Manually adding Name tag.

[webster-chainalysis]

In general we need our tags to propagate to all resources created by the EKS service as part of a managed node group.

[nodesocket]

I see that I can specify Tags for a node group, but it is static. I'd like to apply something like:

Name: eks-stage-worker-${number}

Where ${number} represents the worker number.

[woz5999]

It's extremely painful to see a huge list of unnamed ec2 instances when you're managing multiple node groups or multiple clusters and can't quickly discern which cluster/node group an instance belongs to.

[bhegazy]

Yes as @webster-chainalysis mentioned currently the managed node group tags are not propagated to aws resources.
Not sure should we open a new issue or edit this issue to correctly propose propagating managed node groups tags to aws resources ?

[tobdub]

There is an issue for propagating all tags: https://github.com/aws/containers-roadmap/issues/374

[bhegazy]

Thanks @tobdub I did not see that 👍

[TBBle]

This is different from #374, as I would not expect the NodeGroup's 'Name' tag to propagate down to each EC2 instance, but a unique Name to be generated for each EC2 instance, probably _based_ on the NodeGroup's 'Name' tag. Similar thinking to what https://github.com/terraform-providers/terraform-provider-aws/issues/12451 was looking for, I think.

[rwolfson]

Although it's not a perfect fix for the issue described here, the new launch template enhancement (#585) looks like it allows setting static tags for instances and volumes in an EKS managed node group. Caveats include that the tags are static per launch template (i.e., you would likely have a LT per node group or cluster), and it's possible that it's a heavy-handed approach for folks that don't need the rest of the LT knobs.

[sanpedroadrian28]

hello, has there been a fix on this case? it's really a pain to keep naming blank EC2 instances of the EKS node group even if they are being referenced on the tags section of the EC2.

[juan-caylent]

There is a workaround:
https://stackoverflow.com/questions/63328382/how-can-i-name-eks-worker-nodes-provisioned-with-terraform

But if you need to specify multiple node groups, not sure how to do it.

[acesir]

As everyone else has clearly pointed out, using launch templates just to propagate the Name tag is pretty horrendous. Is there any news on resolving this issue?

[MichaelX99]

I'm not exactly sure which issue to put this on so I'll probably but it in a decent number of issues but not having propagating Tags to all EKS cluster resources effectively makes this entire service useless. If you can't tag your resources you can't separate out costs between different programs and therefore will never be allowed by a program manager and rightfully so. This needs to be fixed ASAP.