<p>I keep getting this error when I try to setup liveness &amp; readiness prob for my awx_web container</p>
<pre><code>Liveness probe failed: Get http://POD_IP:8052/: dial tcp POD_IP:8052: connect: connection refused
</code></pre>
<p>Liveness &amp; Readiness section in my deployment for the container awx_web</p>
<pre><code>          ports:
          - name: http
            containerPort: 8052 # the port of the container awx_web
            protocol: TCP
          livenessProbe:
            httpGet:
              path: /
              port: 8052
            initialDelaySeconds: 5
            periodSeconds: 5
          readinessProbe:
            httpGet:
              path: /
              port: 8052
            initialDelaySeconds: 5
            periodSeconds: 5
</code></pre>
<p>if I test if the port 8052 is open or not from another pod in the same namespace as the pod that contains the container awx_web or if I test using a container deployed in the same pod as the container awx_web i get this (port is open)</p>
<pre><code>/ # nc -vz POD_IP 8052
POD_IP  (POD_IP :8052) open
</code></pre>
<p>I get the same result (port 8052 is open) if I use netcat (nc) from the worker node where pod containing the container awx_web is deployed.</p>
<p>for info I use a NodePort service that redirect traffic to that container (awx_web)</p>
<pre><code>type: NodePort
ports:
- name: http
  port: 80
  targetPort: 8052
  nodePort: 30100
</code></pre>

Abderrahmane
<p>I recreated your issue and it looks like your problem is caused by too small value of <code>initialDelaySeconds</code> for the liveness probe.</p>
<p>It takes more than 5s for awx container to open 8052 port.
You need to wait a bit longer for it to start. I have found out that setting it to 15s is enough for me, but you may require some tweaking.</p>
