Closed brian1917 closed 1 month ago
@brian1917
Updating to the latest image nodepool should resolve this issue. The fix is in 2023.02.09 image or later.
Action required from @Azure/aks-pm
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Close this issue as it was answered in https://github.com/Azure/AKS/issues/3452#issuecomment-1456036477
Describe the bug AKS clusters are coming online with duplicate machineIDs for all nodes.
To Reproduce
kubectl get nodes -o yaml | grep machineID
and observe output likeIt seems all AKS cluster nodes (even on different clusters) have the same machineIDs.
Expected behavior Unique machineIDs on each node.
Environment (please complete the following information):