-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Ability to have exclusive tags for just the eks cluster resouces #1470
Comments
Signed-off-by: mmerril8 <[email protected]>
Signed-off-by: mmerril8 <[email protected]>
Signed-off-by: mmerril8 <[email protected]>
Hi @antonbabenko , let me know if this is something that can be looked at for a future release. Basically, I have a use case where I just need to be able to tag the EKS clusters with very specific tags, and the other resources that are created along the EKS cluster do not need that tag. |
Hi @mmerrill3 ! @barryib is the lead maintainer of this module and he will reply when time permits. PS: I guess it is a summer break for many of us who maintain terraform-aws-modules, so don't expect an immediate response. |
Signed-off-by: mmerril8 <[email protected]>
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS? No
Is your request related to a problem? No
Describe the solution you'd like.
As a terraform user, I'd like to give my eks cluster resource a set of tags that are exclusive to just the cluster resource
Describe alternatives you've considered.
I have forked this project and I created a new variable in variables.tf, specific for the cluster tags
Additional context
Tags as placed on all the resources, which is verbose, and chews into limits of tagging in AWS. I'd like to the ability to put tags only on the EKS cluster itself.
The text was updated successfully, but these errors were encountered: