1

i have a cluster where i have aad-pod-identity installed like the instructions found here: https://azure.github.io/aad-pod-identity/docs/getting-started/installation/#helm enter image description here

That seemed to work fine for the most part, but because of other issues i ended up running az aks create -g myResourceGroup -n myAKSCluster --enable-pod-identity as you find here https://learn.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity

This seems to have installed an additional nmi, through a daemonset: enter image description here

and because of this, i'm getting a CrashLoopBackOff from this nmi pod: enter image description here

the logs say the issue is :

error creating http server: listen tcp 127.0.0.1:2579: bind: address already in use

I've tried deleting the nmi daemonset, thinking that having that and the aad-pod-identity deploy might be the same thing done 2 different ways, but the daemonset keeps ressurecting somehow. How do i clean up this issue? Thanks

Phil
  • 1,852
  • 2
  • 28
  • 55

0 Answers0