Closed 1stewart closed 2 years ago
Nevermind, got it working. I was missing the basic aad-pod-identity stuff (binding label, identity, identitybinding) since I assumed the config in azure.json was sufficient. I could see the same error on the nmi pod, so after reviewing: https://github.com/kubernetes-sigs/external-dns/issues/1456, and the required steps for an MSI in https://azure.github.io/aad-pod-identity/docs/demo/standard_walkthrough/, it works as expected.
Is this an issue with the documentation (https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure.md) missing the aad-pod-identity parts (there's no label in the deployment example), or would those examples work on newer AKS versions/via the extension, which perhaps could be made clearer in the guide how to verify the environment is suitable.
What happened:
Receiving below error when running with a managed identity
What you expected to happen
Retrieve DNS records
How to reproduce it (as minimally and precisely as possible):
Get managed identity used by kubeletidentity (managed identity given contributor to whole subscription containing AKS/VMSS & DNS zone for testing)
Set up secret content as below:
Deploy via helm with debug level, gather logs
Setup works as expected when using a service principal with same permissions to subscription, in same tenant, with config like below:
Anything else we need to know?:
We've got basic connectivity to the internal IP
Environment:
external-dns --version
): 0.10.2