Allow to add a list of tags to the azure resources created by the NodePool. This can be achieved by using metadata labels or even a new section called "tags" under the NodePool template spec.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Many Azure subscriptions have Azure Policies around Tagging of the resources and the policy would deny the creation of VMs if specific tags are not present. Because of this, its impossible for Karpenter to create VMs in such subscriptions unless there is a policy exception created for this.
Are you currently working around this issue?
Current workaround is to create an exception of the Azure Policy on the required resource groups
Additional Context
No response
Attachments
No response
Community Note
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
Tell us about your request
Allow to add a list of tags to the azure resources created by the NodePool. This can be achieved by using metadata labels or even a new section called "tags" under the NodePool template spec.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Many Azure subscriptions have Azure Policies around Tagging of the resources and the policy would deny the creation of VMs if specific tags are not present. Because of this, its impossible for Karpenter to create VMs in such subscriptions unless there is a policy exception created for this.
Are you currently working around this issue?
Current workaround is to create an exception of the Azure Policy on the required resource groups
Additional Context
No response
Attachments
No response
Community Note