<p>I upgrade AKS using Azure portal from 1.23.5 to 1.24.9. This part finished properly (or so I assumed) based on below status on Azure portal.
<a href="https://i.stack.imgur.com/RuT23.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RuT23.png" alt="enter image description here" /></a></p>
<p>I continued with 1.24.9 to 1.25.5. This time it worked partly. Azure portal shows 1.25.5 for nodepool with provision state &quot;Failed&quot;. While nodes are still at 1.24.9.</p>
<p>I found that some nodes were having issues connecting to network including outside e.g. github as well as internal &quot;services&quot;. For some reason it is intermittent issue. On same node it sometime works and sometimes not. (I had pods running on each node with python.)</p>
<p><a href="https://i.stack.imgur.com/Yy6M5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Yy6M5.png" alt="enter image description here" /></a></p>
<p>Each node has cluster IP in resolv.conf
<a href="https://i.stack.imgur.com/bipoQ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/bipoQ.png" alt="enter image description here" /></a></p>
<p>One of the question on SO had a hint about <code>ingress-nginx</code> compatibility. I found that I had an incompatible version. So I upgraded it to <a href="https://github.com/kubernetes/ingress-nginx" rel="nofollow noreferrer">1.6.4 which is compatible with 1.24 and 1.25 both</a></p>
<p>But this network issue still persists. I am not sure if this is because AKS provisioning state of &quot;Failed&quot;. Connectivity check for this cluster in Azure portal is Success. Only issue reported in Azure portal diagnostics is nodepool provisioning state.
<a href="https://i.stack.imgur.com/gPyiy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/gPyiy.png" alt="enter image description here" /></a></p>
<p>is there anything I need to do after <code>ingress-nginx</code> upgrade for all nodes/pods to get the new config?
Or is there a way to re-trigger this upgrade? although I am not sure why, but just assuming that it may reset the configs on all nodes and might work.</p>

arundeep78
<p>Ok, posting the solution and journey to it here, so just in case someone comes across similar issue.</p>
<p>There was a network issue in the cluster after the upgrade. This was the reason all pods had DNS issue. Due to these network issues metrics-server was not in running state and it's pdb allowed disruption remained at 0 and it was causing <code>PodDrainFaulure</code> errors while upgrading the node.</p>
<p>I was able to force the upgrade to upgrade all nodes to 1.25.5 by running the command <code>az aks nodepool upgrade -n agentpool -g rg_name --cluster-name aks_name --node-image-only</code> . However, after executing this, I had to keep on <a href="https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/error-code-poddrainfailure" rel="nofollow noreferrer">deleting the pdb</a> to get all the nodes to upgrade.</p>
<p>This helped to get control plane and all nodes to reach 1.25.5 version, however overall status still remained in failed(Running) state. This was solved by triggering another upgrade with --cluster-plane-only flag</p>
<pre><code>   --resource-group &lt;ResourceGroupName&gt; --name &lt;AKSClusterName&gt; \
   --control-plane-only \
   --kubernetes-version &lt;KubernetesVersion&gt;
</code></pre>
<p>However, this did not solve the core networking issues, as starting from metrics server to application pods, all were failing trying to resolve hostnames. Interesting thing was that internal services were not reachable at all, however outside network e.g. github.com, microsoft.com etc would work intermittently.</p>
<p>Based on <a href="https://github.com/Azure/AKS/issues/2903" rel="nofollow noreferrer">AKS issue 2903</a> and related <a href="https://github.com/kubernetes/ingress-nginx/issues/8501" rel="nofollow noreferrer">ingress-nginx issue 8501</a> found that after k8s 1.24 ingress-nginx needs special annotation to keep health probes running properly. had to update helm with below command</p>
<pre><code>helm upgrade ingress-nginx ingress-nginx/ingress-nginx \
  --reuse-values \
  --namespace &lt;NAMESPACE&gt; \
  --set controller.service.annotations.&quot;service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path&quot;=/healthz
</code></pre>
<p>This did get the Azure aks health dashboard and metrics server to show as running state, but it did not solve the underlying network issue. used all the scenarios and commands mentioned in all sections of <a href="https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/basic-troubleshooting-outbound-connections" rel="nofollow noreferrer">MS troubleshooting guide for outbound connections</a> to narrow down that issue is somehow with <code>kube-dns</code> service and CoreDNS pods.</p>
<p>as DNS resolution would work if upstreaming nameserver directly to coreDNS pod IP (need to run on the same node) OR public DNS, but it will fail if it was using <code>kube-dns</code> service ip as configured in <code>resolv.conf</code></p>
<pre><code>jovyan@elyra-web-59f899c447-xw5x2:~$ host -a microsoft.com
Trying &quot;microsoft.com.elyra-airflow.svc.cluster.local&quot;
;; connection timed out; no servers could be reached

jovyan@elyra-web-59f899c447-xw5x2:~$ nslookup microsoft.com
;; connection timed out; no servers could be reached

jovyan@elyra-web-59f899c447-xw5x2:~$ nslookup microsoft.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
Name:   microsoft.com
Address: 20.103.85.33
Name:   microsoft.com
Address: 20.112.52.29
Name:   microsoft.com
Address: 20.81.111.85
Name:   microsoft.com
Address: 20.84.181.62
Name:   microsoft.com
Address: 20.53.203.50

</code></pre>
<p>I restarted coreDNS, konnectivity-agent and so on, but no help.
At the end found a <a href="https://github.com/Azure/AKS/issues/1320#issuecomment-555897357" rel="nofollow noreferrer">hint from AKS issue 1320</a> which helped solved the issue. Even though this issue is related to k8s version 1.13 thus suggesting it was not a version specific problem. I deleted ALL pods from namespace <code>kube-system</code> at once. Immediately after these pods were up and running, DNS issue was gone and all is working as before.</p>
<p>Phew,  this was some journey of 5 days to get it solved. Looking forward to next upgrade in March now !</p>
