Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support tagging of instances, ASGs, launch config, etc. #74

Closed
lukehoban opened this issue Feb 28, 2019 · 5 comments · Fixed by #122
Closed

Support tagging of instances, ASGs, launch config, etc. #74

lukehoban opened this issue Feb 28, 2019 · 5 comments · Fixed by #122
Assignees
Labels
customer/feedback Feedback from customers kind/enhancement Improvements or new features
Milestone

Comments

@lukehoban
Copy link
Member

We should expose options for adding custom tags to these (and any other) resources, and may want to automatically at least add Name tags as a default.

@lukehoban lukehoban added this to the 0.21 milestone Feb 28, 2019
@metral
Copy link
Contributor

metral commented Feb 28, 2019

@metral metral modified the milestones: 0.21, 0.22 Mar 6, 2019
@lukehoban lukehoban modified the milestones: 0.22, 0.23 Apr 12, 2019
@naineel
Copy link
Contributor

naineel commented Apr 17, 2019

This is super important for us. Billing is a big use case which we need to enable

@joeduffy
Copy link
Member

Note that the EKS cluster resource in AWS itself doesn't appear to support tagging, at least based on the AWS API (https://docs.aws.amazon.com/sdk-for-go/api/service/eks/#CreateClusterInput) and AWS CloudFormation (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-eks-cluster.html) documentation.

It probably makes sense to

  1. Expose a tags option that auto-tags all resources it can possibly tag (like the instances, security groups, etc)
  2. Expose a single xTags option, for each resource, x, that supports tagging, in case you want more fine grained control (e.g., instanceTags, securityGroupTags, etc)

I assume AWS will add tagging support to EKS sometime soon, in which case (1) would just start applying them auto-magically on upgrade, and (2) would lead to a separate clusterTags option.

@Lavender-Ding
Copy link

Adding custom tags on Node Group created by EKS is needed to enable Cluster Autoscaler on our side, before this is resolved, is there any way to work around it? Something like get the existing nodegroup and add tags to it.

@lukehoban
Copy link
Member Author

Adding custom tags on Node Group created by EKS is needed to enable Cluster Autoscaler on our side

I believe in this particular case you need to add tags to the AutoScalingGroup. In particular these two tags:

k8s.io/cluster-autoscaler/enabled
k8s.io/cluster-autoscaler/<ClusterName>

Currently I don't believe there is anyway to do that yourself. But a PR to this package to enable that should be fairly straightforward, so if you want to contribute it we'd be happy to review and merge a PR. Else this is something we'll be looking into very soon ourselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer/feedback Feedback from customers kind/enhancement Improvements or new features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants