Description
What problem are you trying to solve?
Currently, tags can only be defined in the EC2NodeClass. When multiple NodePools share the same EC2NodeClass but require different tags, the only option is to create separate EC2NodeClasses for each variation.
For example, I may have 5 NodePools with identical configuration, but each one needs a different value for a single tag (such as cost allocation, ownership, or environment metadata). This forces me to create and maintain 5 nearly identical EC2NodeClasses, increasing duplication and operational overhead.
It would be useful if NodePools could define tags that override or merge with the tags defined in the referenced EC2NodeClass. This would allow a common EC2NodeClass to be reused while still enabling per-NodePool customization.
How important is this feature to you?
This would significantly simplify NodePool management and reduce configuration duplication. It would also make tagging strategies easier to implement, especially in environments where tags are used for cost allocation, ownership tracking, automation, or governance purposes.
- Please vote on this issue by adding a 👍 reaction 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
Description
What problem are you trying to solve?
Currently, tags can only be defined in the EC2NodeClass. When multiple NodePools share the same EC2NodeClass but require different tags, the only option is to create separate EC2NodeClasses for each variation.
For example, I may have 5 NodePools with identical configuration, but each one needs a different value for a single tag (such as cost allocation, ownership, or environment metadata). This forces me to create and maintain 5 nearly identical EC2NodeClasses, increasing duplication and operational overhead.
It would be useful if NodePools could define tags that override or merge with the tags defined in the referenced EC2NodeClass. This would allow a common EC2NodeClass to be reused while still enabling per-NodePool customization.
How important is this feature to you?
This would significantly simplify NodePool management and reduce configuration duplication. It would also make tagging strategies easier to implement, especially in environments where tags are used for cost allocation, ownership tracking, automation, or governance purposes.