<p>It looks like it happens randomly, but when I bring up Minikube and start working with it, after a while (can't say exactly how long, it changes every time) I suddenly can't use commands with kubectl and get an error -</p>

<blockquote>
  <p>Unable to connect to the server: dial tcp 192.168.1.20:8443: connect:
  no route to host</p>
</blockquote>

<p>I tried to find a solution on the Internet but couldn't find the reason why this was happening, and I can't fix it other than deleting a minikube with</p>

<pre><code>sudo minikube delete
</code></pre>

<p>And then restarted with</p>

<pre><code>sudo minikube start --vm-driver=none
</code></pre>

<p>Anyone come across this and can help?</p>

<p>I had similar behaviour when my <strong>minikube</strong> was overloaded. I was spinning up a <strong>minikube</strong> with default settings, but then deploying too much workloads on it. At some point I get the same error.</p>
<p>Try tracking the load on your node with:</p>
<pre><code>kubectl top nodes
</code></pre>
<p>or</p>
<pre><code>kubectl top pods --all-namespaces
</code></pre>
<p>I found that running <strong>minikube</strong> with more resources helped me.</p>
<p>My new default setup is:</p>
<pre><code>minikube start --cpus 4 --memory 8192
</code></pre>
