Containers-roadmap: [EKS]: EKS Cluster Tagging Propagation

[tabern]

Tell us about your request
Ability to propogate EKS cluster tags to EC2 resources (instances, autoscaling groups, load balancers) used as part of the cluster. This will help with resource organization and cost allocation within your AWS account.

Feedback requested
Should we expand the scope of this to include propagating K8s labels to AWS tags and giving you the ability to assign labels used for resources within certain namespaces, services, etc as AWS tags on related resources? This is one path to improving cost allocation capabilities withing AWS and K8s.

[tdmalone]

Should we expand the scope of this to include propagating K8s labels to AWS tags and giving you the ability to assign labels used for resources within certain namespaces, services, etc as AWS tags on related resources?

Yes - I think this is a great idea. It would be a really ace integration and, other than just for cost allocation, it would make it easier to programatically select k8s-managed resources in custom ops scripting.

[xanderbo]

First, make it work. Then make it work better. Expanded scope is great as long as it does not delay the release date.

[gmagella-ca]

I was just deploying a ALB using ALB Ingress controller and I notice that we do have the ability to tag it by annotating the Ingress.

annotations:
alb.ingress.kubernetes.io/tags: auto-delete=no,owner=gmagella,app=my-1st-flask

Looks like it does tag the ALB and the TG. But I couldn't help but notice that it didn't update tags on the ALB, when changing the Ingress details. (it does update the TG tags though).

Let me know if this is not the right venue to comment on this, and I'll take appropriate actions.

[i5okie]

Would be nice to propagate these tags to EBS volumes too.

[cdenneen]

Did the tags used to work? I thought they did but all my nodeGroups now no longer have the tags specified in the eksctl configuration. Need to get these tags back in as they are used for Cost reporting.

[tabern]

[edit] eksctl can propagate tags for self-managed and managed node groups. however if you use CFN or the API, tags for EKS managed node groups do not propagate. We are working on enabling tag propagation for EKS clusters from the cluster down to nodes through the EKS API.

[jasongaunt]

Hi @tabern is there anymore news on this please? ♥

[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.