<p>I have installed CP-Kafka locally in K8s for Docker desktop. After a day or so the Contol Center remains in a wierd state. The service is visible:</p>

<pre><code>$ kgsvc -l app=cp-control-center -o wide
NAME                             TYPE       CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE   SELECTOR
officefriday-cp-control-center   NodePort   10.106.121.181   &lt;none&gt;        9021:30569/TCP   15h   app=cp-control-center,release=officefriday
</code></pre>

<p>The pod for the service is not there:</p>

<pre><code>$ kgpo
NAME                                               READY   STATUS    RESTARTS   AGE
curl                                               1/1     Running   0          12d
dnsutils                                           1/1     Running   0          14d
kafka-client                                       1/1     Running   0          40h
officefriday-cp-kafka-0                            2/2     Running   0          14h
officefriday-cp-kafka-1                            2/2     Running   0          14h
officefriday-cp-kafka-2                            2/2     Running   0          14h
officefriday-cp-kafka-connect-c77bd598c-x42tj      2/2     Running   1          15h
officefriday-cp-kafka-rest-6559b7588b-ld8wk        2/2     Running   0          15h
officefriday-cp-ksql-server-7fcdcdccd5-lwt2w       2/2     Running   0          15h
officefriday-cp-schema-registry-84855ff8f6-v6p28   2/2     Running   1          15h
officefriday-cp-zookeeper-0                        2/2     Running   0          15h
officefriday-cp-zookeeper-1                        2/2     Running   0          15h
officefriday-cp-zookeeper-2                        2/2     Running   0          15h
</code></pre>

<p>But the problem is that for K8s there is nothing wrong with it.</p>

<p>Now the CC service is still reachable:</p>

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

<p>I have restarted Docker and all the rest works apart from the missing pod.</p>

<p>How can one troubleshoot sth like that? Not much good hints out there.</p>

<p>Thnx!</p>

<p>It is very hard to say what might be the cause of this particular problem without any relevant logs or error messages. However, there are some recommended steps that should be taken in order to debug this and any similar problem in the future.</p>
<p>According to the <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/" rel="nofollow noreferrer">official documentation</a> you should start from:</p>
<ul>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-pods" rel="nofollow noreferrer">Debugging Pods</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-replication-controllers" rel="nofollow noreferrer">Debugging Replication Controllers</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-services" rel="nofollow noreferrer">Debugging Services</a></p>
</li>
</ul>
<p>Also, it is strongly suggested to <a href="https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#examine-pod-logs" rel="nofollow noreferrer">examine Pod logs</a> if possible.</p>
<p>I hope this helps to solve your issue. Please let me know what are your findings so I could help further if needed.</p>
