<p>I have started a pod with an angular app in it and it is healthy with no errors when I do kubectl describe pod.</p>
<p>However, when I curl to ingress route I get a 502 bad gateway.</p>
<p>I tried exec into angular pod and do a curl localhost:4200 and I get: Failed to connect to localhost port 4200: Connection refused.</p>
<p>Weirdly enough when i do kubectl logs podname I see nothing and I thought I always see something here, not sure.</p>
<p>Question now is, do I have overlooked something?</p>
<ul>
<li>How do I check if angular app is working inside the pod?</li>
<li>What is the location of the logfile you see normally when you npm start an app?</li>
</ul>
<p>I havent posted any yaml files, because I think the problem lies with the angular app itself (the curl localhost:4200 hinted me to that).</p>

furion2000
<p>your container configuration is not set up correctly to start the service?</p>
<p>you have a config like:</p>
<pre><code>apiVersion: v1
kind: Pod
metadata:
  name: my-angular-app
spec:
  containers:
  - name: my-angular-app
    image: nginx:latest
    ports:
    - containerPort: 80
</code></pre>
<p>it should also have an command like <code>command: [&quot;nginx&quot;, &quot;-g&quot;, &quot;daemon off;&quot;]</code> to actually start the service.</p>
<p>if it does, then you have logs indicating if it is starting and the current description should indicate the correct port:</p>
<p>You can check the logs at the container level by using <code>kubectl logs -f podname -c containername</code> to see if there are any errors or issues that are preventing the app from starting</p>
<p>You can check the port by running <code>kubectl describe pod podname</code> and looking at the &quot;Containers&quot; section.</p>
