Open nicholasgcoles opened 4 years ago
This feature + this announcement about Cost Categories supporting split charge rules is a game changer for being able to support different organizations/development teams running on the same EKS cluster. Looking forward to this...
I couldn't agree more @hspencer77 ! Any updates on this issue?
Any updates on this issue? - Would strongly need the tagging capabilities of running pods on fargate for billing our customers.
I was looking for ways to have AWS Lambda tag the Fargate instances, however, any instances created by EKS with a FargateProfile are not shown in EC2.
Is there any other API where I can add the required tags for cost allocation?
Just ran into this problem as well, would love to see this get added
Hi peeps! We'd love this feature as well :pray:
bump, encountering the same issue
bump, still encountering the issue
We are also encountering this. I have raised the issue via our Enterprise support plan, and got the following reply:
Our internal team has also noted this feature and are working towards implementing this as soon as they can!
I must also note that PFRs are not necessarily gauranteed and do not have a definite timeline promise. I thank you for your patience while our teams work towards implementing this feature for you and other EKS fargate customers.
Community Note
Tell us about your request When adding a Fargate Profile in EKS you are able to add tags to it. However, it seems that these tags do not propagate to billing. My assumption was that if you tagged a Fargate Profile, all Fargate containers which run in EKS would then have the relevant tag in their corresponding AWS billing line item.
If this is not the case, what are those tags used for? And is there possibly a preferred way to tag Fargate containers running in EKS?
Which service(s) is this request for? Fargate for EKS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Trying to differentiate between different Fargate tasks / containers using the tags in the Fargate Profiles.
Are you currently working around this issue? Currently remains unsolved