[EKS]: EKS Cluster Tagging Propagation
**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.
Posted by tabern on Jun 17, 2019, 4:16 AM
Tags
Related issues
- Everything is too expensive for European bureaucrats.
- Yeah, the plan is far too expensive for what it provides.
- Crashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
- /dev/random is much too expensive for this.
- Yeah, this always bugged me.
- A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
pricing (Other)
Everything is too expensive for European bureaucrats.
NewYeah, the plan is far too expensive for what it provides.
NewCrashed demand after one of the big AI labs (probably Anthropic because they focus way too hard on expensive frontier models) become inso...
New/dev/random is much too expensive for this.
Yeah, this always bugged me.
A year ago, I had the opinion that it'd be too expensive for developers to support offline mode, peer to peer, or community servers after...
The weird thing about this product is that its biggest competitor is "an old ipad." I feel like most of their target customer base alread...
There's a talk from Travis Kalanick recently on a podcast about this.
[EKS]: EKS Cluster Tagging Propagation
**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.
Comments (0)
No comments yet. Start the discussion.