<p>I am using a Windows 10 Pro machine.  </p>

<p>When I run <code>netstat</code>, it is showing <code>kubernetes:port</code> as foreign address in active connections.  </p>

<p>What does this mean? I have checked and there is no kubernetes cluster running on my machine.  </p>

<p>How do I close these connections?</p>

<p><a href="https://i.stack.imgur.com/ZpocC.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ZpocC.png" alt="enter image description here"></a>  </p>

<p>Minikube status:</p>

<pre><code>$ minikube status
host:
kubelet:
apiserver:
kubectl:
</code></pre>

Shubham Chadokar
<p>That happens because of the way <code>netstat</code> renders output. It has nothing to do with actual Kubernetes.</p>

<p>I have Docker Desktop for Windows and it adds this to the hosts file:</p>

<pre><code># Added by Docker Desktop
192.168.43.196 host.docker.internal
192.168.43.196 gateway.docker.internal
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section
</code></pre>

<p>There is a record which maps <code>127.0.0.1</code> to <code>kubernetes.docker.internal</code>. When <code>netstat</code> renders its output, it resolves foreign address and it looks at the hosts file and sees this record. It says <code>kubernetes</code> and that is what you see in the console. You can try to change it to</p>

<pre><code>127.0.0.1 tomato.docker.internal
</code></pre>

<p>With this, <code>netstat</code> will print:</p>

<pre><code>  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:6940         tomato:6941            ESTABLISHED
  TCP    127.0.0.1:6941         tomato:6940            ESTABLISHED
  TCP    127.0.0.1:8080         tomato:40347           ESTABLISHED
  TCP    127.0.0.1:8080         tomato:40348           ESTABLISHED
  TCP    127.0.0.1:8080         tomato:40349           ESTABLISHED
</code></pre>

<p>So what actually happens is there are connections from localhost to localhost (<code>netstat -b</code> will show apps that create them). Nothing to do with Kubernetes.</p>
