kk-bavenkatachalam
commented
1 year ago Yeah, AKS nodepool should expose underlying vmss name. It would be useful in assigning new user defined identites which in turn would be used for accessing keyvault secrets/keys/certificates. https://learn.microsoft.com/en-us/azure/aks/csi-secrets-store-identity-access#use-a-user-assigned-managed-identity
Currently, we need to access MC_aksname_rgname resource group to get the underlying vmss. But if nodepool exposes vmss name there is no need to do this additional step.
There is also a similar request in the hashicorp/terraform-provider-azurerm repository but it cannot be fulfilled if AKS does not support this feature. https://github.com/hashicorp/terraform-provider-azurerm/issues/6217
ghost
microsoft-github-policy-service[bot]
Is your feature request related to a problem? Please describe.
Each Node in AKS cluster have corresponding VirtualMachine/ VirtualMachineScaleSet. This information should be exposed via label on the node object, to make it easy to identify the underlying resource in azure.
It would be needed to cross reference metrics from Azure Metrics portal with other metrics, exposed via i.e. kube-state-metrics. Currently, from azure metric we can get VMName dimension, which does not match node name. Example:
nodename -aks-001-xxxxx-vmss000046VMName-aks-001-xxxxx-vmss_150Additional context https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/2610