Error connecting AKS with ACR

Kopl 166 Reputation points
2022-08-30T11:33:12.563+00:00

Hello team,

My AKS was connected to ACR for months now and I was always able to pull images from ACR. However, this morning I am not able for some reason.

I tried using this command:

az aks update -n myAKSCluster -g myResourceGroup --attach-acr <acr-name>

However, without success. Could you please help?

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
396 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,869 questions

12 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sean Hannan 1 Reputation point
    2022-08-31T06:55:31.617+00:00

    Just as a follow up we have restarted the instances and VMSS separately. This has resolved the failed to pull image errors however our workload is still failing likely due to issues connecting to other required instances caused by the same issue

    0 comments
  2. Eugene Terblanche 1 Reputation point
    2022-08-31T07:34:38.437+00:00

    We are experiencing the same Issue in South Africa North DC

    0 comments
  3. Nadav Ben Haim 496 Reputation points Microsoft Employee
    2022-08-31T07:54:19.17+00:00

    This issue is now being mitigated [remediated].

  4. Eugene Terblanche 1 Reputation point
    2022-08-31T08:03:02.393+00:00

    "A potential workaround customers can consider is to reboot impacted VM instances so that they receive a fresh DHCP lease and new DNS resolver(s). If you are running a VM with Ubuntu 18.04 image, and you are experiencing connectivity issues, you can evaluate the above mitigation options.

    Our engineering team deployed an auto-remediation for AKS clusters in all regions, and noticed a substantial progress with impacted clusters recovering to a healthy state. However, it was determined that there were a subset of cases where the AKS nodes were not covered by the auto-remediation detection, and were not fixed as a result. Engineers have developed and are in the process of deploying a fix to these nodes that were not mitigated in the earlier iteration. We are making steady progress on this deployment and will continue to share an update."

    0 comments
  5. Kopl 166 Reputation points
    2022-08-31T09:35:21.983+00:00

    The workaround we used to circumvent the DNS issue was to shut down and restart the affected AKS node pool. Everything seems to work fine after this workaround