<p>My <code>kube-controller-manager</code>keeps staying on <code>CrashLoopBackOff</code> status. </p>

<p>I found this upon looking in the logs of the pod:
<code>failed to create listener: failed to listen on 0.0.0.0:10252: listen tcp 0.0.0.0:10252: bind: address already in use</code></p>

<p>Then I stumbled upon this article who fortunately was able to find a fix for it. Where he killed the process using the port and restarted his <code>kube-controller-manager</code> pod. <a href="https://medium.com/@deepeshtripathi/kubernetes-controller-pod-crashloopbackoff-resolved-16aaa1c27cfc" rel="nofollow noreferrer">https://medium.com/@deepeshtripathi/kubernetes-controller-pod-crashloopbackoff-resolved-16aaa1c27cfc</a></p>

<p>So I did follow the steps he made. When I have tried to get into the master node to find which process is using this port, I can't see anything that uses it.</p>

<pre><code>root@ip:/# netstat -tunlp | grep 1025 
tcp6       0      0 :::10250                :::*                    LISTEN      1598/kubelet    
tcp6       0      0 :::10251                :::*                    LISTEN      7472/kube-scheduler
tcp6       0      0 :::10255                :::*                    LISTEN      1598/kubelet    
tcp6       0      0 :::10256                :::*                    LISTEN      5629/kube-proxy 
</code></pre>

<p>Is there anyone else know any solution on how to fix this?</p>

<blockquote>
  <p>failed to create listener: failed to listen on 0.0.0.0:10252: listen tcp 0.0.0.0:10252: bind: address already in use</p>
</blockquote>

<p>According to the error message port <code>10252</code> is in use. So need to stop listening on this port. You can do that by running</p>

<p><code>fuser -k 10252/tcp</code></p>
