K8s 错误：ImagePullBackOff || 读取：连接被拒绝

Question

在部署我们为 Pod 获取 ImagePullBackOff 时，您能提供帮助吗？

运行时kubectl get <pod-name> -n namespace -o yaml出现以下错误。

containerStatuses:
  - image: mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644
    imageID: ""
    lastState: {}
    name: dmd-base
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        message: Back-off pulling image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644"
        reason: ImagePullBackOff
  hostIP: x.x.x.53
  phase: Pending
  podIP: x.x.x.237

并运行时kubectl describe pod <pod-name> -n namespace收到以下错误信息

  Normal   Scheduled  85m                  default-scheduler  Successfully assigned dmd-int/app-app-base-5b4b75756c-lrcp6 to aks-agentpool-35064155-vmss00000a
  Warning  Failed     85m                  kubelet            Failed to pull image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  [rpc error: code = Unknown desc = failed to pull and unpack image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  failed to resolve reference "mycontainer-registry.io/commpany/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  failed to do request: Head "https://mycontainer-registry.azurecr.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  dial tcp: lookup mycontainer-registry.azurecr.io on [::1]:53: read udp [::1]:56109->[::1]:53: read: connection refused, 
  rpc error: code = Unknown desc = failed to pull and unpack image "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  failed to resolve reference "mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  failed to do request: Head "https://mycontainer-registry.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644": 
  dial tcp: lookup mycontainer-registry.io on [::1]:53: read udp [::1]:60759->[::1]:53: read: connection refused]`

从描述的日志中，我可以看到问题出在连接上，但我无法判断连接问题出在哪里，我们在 Azure 上的 Kubernetes 集群中运行应用程序。

如果有人遇到过这个问题，您可以帮忙吗？该应用程序在过去几个月中一直成功运行，我们今天早上才收到这个问题。

Answer 1

今天多个区域出现已知的 Azure 中断。一些 DNS 问题也会影响图像拉取。 https://status.azure.com/en-us/status