<p>Before I could run this command <code>kubectl logs &lt;pod&gt;</code> without issue for many days/versions. However, after I pushed another image and deployed recently, I faced below error:</p>

<blockquote>
  <p>Error from server: Get <a href="https://aks-agentpool-xxx-0:10250/containerLogs/default/" rel="noreferrer">https://aks-agentpool-xxx-0:10250/containerLogs/default/</a>&lt;-pod->/&lt;-service->: dial tcp 10.240.0.4:10250: i/o timeout</p>
</blockquote>

<p>I tried to re-build and re-deploy but failed.</p>

<p>Below was the Node info for reference:
<a href="https://i.stack.imgur.com/NqxBA.png" rel="noreferrer"><img src="https://i.stack.imgur.com/NqxBA.png" alt="Node Info"></a></p>

<p>Not sure if your issue is caused by the problem described in this <a href="https://learn.microsoft.com/en-us/azure/aks/troubleshooting#i-cant-get-logs-by-using-kubectl-logs-or-i-cant-connect-to-the-api-server-im-getting-error-from-server-error-dialing-backend-dial-tcp-what-should-i-do" rel="nofollow noreferrer">troubleshooting</a>. But maybe you can take a try, it shows below:</p>
<blockquote>
<p>Make sure that the default network security group isn't modified and
that both port 22 and 9000 are open for connection to the API server.
Check whether the <code>tunnelfront</code> pod is running in the <code>kube-system</code>
namespace using the <code>kubectl get pods --namespace kube-system</code> command.
If it isn't, force deletion of the pod and it will restart.</p>
</blockquote>
