This repository has been archived by the owner on Oct 12, 2023. It is now read-only.
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
-
One of my AKS-based and Flux-powered test clusters I accidentally lost MIC.
The only aad-pod-identity related pods left were NMI.
TL;TR: What is the canonical way to trigger re-deployment of MIC pods?
What I eventually did was I updated Helm chart of aad-pod-identity from 4.1.10 to 4.1.16 and it triggered re-deployment of the MIC pods, but I wonder, would this command do the trick as well?
az aks upgrade -g rg-contoso-dev -n aks-contoso-uks-dev --enable-pod-identityBeta Was this translation helpful? Give feedback.
All reactions