<p>Can you please assist when deploying we getting ImagePullBackOff for our pods.</p>
<p>running <code>kubectl get &lt;pod-name&gt; -n namespace -o yaml</code> am getting below error.</p>
<pre class="lang-yaml prettyprint-override"><code>containerStatuses:
  - image: mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644
    imageID: &quot;&quot;
    lastState: {}
    name: dmd-base
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        message: Back-off pulling image &quot;mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;
        reason: ImagePullBackOff
  hostIP: x.x.x.53
  phase: Pending
  podIP: x.x.x.237
</code></pre>
<p>and running <code>kubectl describe pod &lt;pod-name&gt; -n namespace</code> am getting below error infomation</p>
<pre class="lang-none prettyprint-override"><code>  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 &quot;mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  [rpc error: code = Unknown desc = failed to pull and unpack image &quot;mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  failed to resolve reference &quot;mycontainer-registry.io/commpany/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  failed to do request: Head &quot;https://mycontainer-registry.azurecr.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  dial tcp: lookup mycontainer-registry.azurecr.io on [::1]:53: read udp [::1]:56109-&gt;[::1]:53: read: connection refused, 
  rpc error: code = Unknown desc = failed to pull and unpack image &quot;mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  failed to resolve reference &quot;mycontainer-registry.io/company/my-app:1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  failed to do request: Head &quot;https://mycontainer-registry.io/v2/company/my-app/manifests/1.0.0-integration-62c7e30532bd430477731a01a962372166fd5644&quot;: 
  dial tcp: lookup mycontainer-registry.io on [::1]:53: read udp [::1]:60759-&gt;[::1]:53: read: connection refused]`
</code></pre>
<p>From the described logs I can see the issue is a connection but I can't tell where the issue is with connectivity, we running our apps in a Kubernetes cluster on Azure.</p>
<p>If anyone has come across this issue can you please assist the application has been running successfully throughout the past months we just got this issue this morning.</p>

Siya Nxuseka
<p>There is a known Azure outage multiple regions today.
Some DNS issue that also affects image pulls.
<a href="https://status.azure.com/en-us/status" rel="noreferrer">https://status.azure.com/en-us/status</a></p>
