Auto generated tags via deployment manifests
When a service is created in AKS such as a load balancer, or a disk, which ties back to an Azure resource, add the ability to tag the resource right in the deployment manifest. For organizations requiring strict tagging policies on resources in their Azure accounts, the creation of resources within AKS leaves un-tagged resources in the account.
The outcome of this would be that you, Microsoft, would be empowering your customers with the ability to dynamically organize your resources in the account as they're dynamically created in AKS.
happened to take a look at this issue, currently 4 tags will be created for azure disk PVC:
3 tags are here:
1 specific tag is here:
One way is add a tags parameter in azure disk storage class, and then when dynamic provision an azure disk, user defined tags will be created in azure disk creation time. Not sure this could be the disired requirement?
Oskar Mamrzynski commented
While this would be nice, you can work around this by using an Azure Automation Account.
Handle any events from the AKS resource group and assign tags to resources as you please.