AKS with Azure NetApp files and Managed Identity

[molten schooner]

I'm trying to use trident on AKS with Azure NetApp Files. It does work when I provide clientID and clientSecret. It does not work when I try with Manage Identity (added in version 23.10). It seems that the managed identity used cannot discover NetApp resources. How can I check which Managed Identity is used? How can I verify if credentials were properly read from azure.json?

I put my logs in attachement.

[molten schooner]

Anybody uses Azure Managed Identity? Is there any way do debug this new feature?

[fervent heron]

Hi Blaz, are you able to open a case with us NetApp and ANF? i see the logs with debug, and error, but would need to investigate it. I see ""Feature check failed, it will not be available." not sure if this is a k8s feature required or ANF, etc..

Reference these links:
• https://learn.microsoft.com/en-us/azure/azure-netapp-files/configure-customer-managed-keys?tabs=azure-portal
• https://docs.netapp.com/us-en/bluexp-setup-admin/concept-accounts-azure.html#initial-azure-credentials
• https://docs.netapp.com/us-en/bluexp-setup-admin/concept-accounts-azure.html#additional-azure-subscriptions-for-a-managed-identity
• https://docs.netapp.com/us-en/trident/trident-use/anf.html#managed-identities-for-aks

[molten schooner]

I can open ANF case on Azure Portal if this helps. It looks like credentials are not read properly or Managed Identity which I do not expect is somehow used by trident-controller.

This is the support case I've just created for Azure NetApp Files (ANF): 2401300050004892