[EKS] [request]: Nodegroup should support tagging ASGs
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> **Tell us about your request** It would be great if we could pass tags to the underlying ASGs (and tell the ASGs to propagate tags) that are created from the managed node groups for EKS so that the underlying instances/volumes are tagged appropriately. **Which service(s) is this request for?** EKS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Currently, managed node groups for EKS do not support propagating tags to ASGs (and therefore the instances) created by the node group. This leads to EC2 instances that are not tagged according to our requirements for tracking cost, and resource ownership.
Posted by bhops on Nov 27, 2019, 3:26 PM
Tags
Related issues
- I got tired of the price hikes of the ad free netflix and finally canceled.
- >This is pathological.
- 1) No, but the tracking needed for targeted ads is also behind a consent wall.
- The attention economy is real, your eyes have value that is surprisingly high, and buying out that attention so you can have a pure you-c...
- > Users don’t care whether the code was written by AI or by hand That's true, but they care deeply about the consequences of that: > ab...
- There's a part of the tech industry that uses what I would call dark influencer techniques.
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
pricing (Marketing)
I got tired of the price hikes of the ad free netflix and finally canceled.
>This is pathological.
1) No, but the tracking needed for targeted ads is also behind a consent wall.
The attention economy is real, your eyes have value that is surprisingly high, and buying out that attention so you can have a pure you-c...
> Users don’t care whether the code was written by AI or by hand That's true, but they care deeply about the consequences of that: > ab...
There's a part of the tech industry that uses what I would call dark influencer techniques.
Author here.
You can either have AI be honest or AI become a marketing tool.
[EKS] [request]: Nodegroup should support tagging ASGs
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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 <!--- Thank you for keeping this note for the community ---> **Tell us about your request** It would be great if we could pass tags to the underlying ASGs (and tell the ASGs to propagate tags) that are created from the managed node groups for EKS so that the underlying instances/volumes are tagged appropriately. **Which service(s) is this request for?** EKS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Currently, managed node groups for EKS do not support propagating tags to ASGs (and therefore the instances) created by the node group. This leads to EC2 instances that are not tagged according to our requirements for tracking cost, and resource ownership.
Comments (0)
No comments yet. Start the discussion.