POD Unhealthy and no connection allowed from outside POD

Hi All,

I have been following the Run Kubernetes instruction page and deploying
using the helm chart.

*I am seeing below when I say describe pod - *
  Normal   Created    89s               kubelet            Created
container james-imap-smtp
  Normal   Started    89s               kubelet            Started
container james-imap-smtp
  Warning  Unhealthy  0s (x4 over 20s)  kubelet            Readiness probe
failed: Get "
http://10.244.161.70:8000/healthcheck/checks/Guice%20application%20lifecycle":
dial tcp 10.244.161.70:8000: connect: connection refused


*When I checked the same from inside the pod - *
C:\Dev\padminisys\github\james-project-james-project-3.8.0\server\apps\distributed-app\helm-chart>kubectl
exec -it james-imap-smtp-86f68c6499-9995j -- sh
# curl
http://10.244.161.70:8000/healthcheck/checks/Guice%20application%20lifecycle
curl: (7) Failed to connect to 10.244.161.70 port 8000: Connection refused

*When I changed the pod IP with localhost, it worked, however, I can't
connect using svc or POD IP from the cluster- *
# curl
http://localhost:8000/healthcheck/checks/Guice%20application%20lifecycle
{"componentName":"Guice application
lifecycle","escapedComponentName":"Guice%20application%20lifecycle","status":"healthy","cause":null}#


*PS: I am only using one POD *james-imap-smtp, not using jmap.

Please help me to get James running on the Kubernetes cluster.

I appreciate any help you can provide.
Gaurav Tyagi

-- 
*Padmini Systems Private Limited* puts the security of the client at a high 
priority. Therefore, we have put efforts into ensuring that the message is 
error and virus-free. Unfortunately, full security of the email cannot be 
ensured as, despite our efforts, the data included in emails could be 
infected, intercepted, or corrupted. Therefore, the recipient should check 
the email for threats with proper software, as the sender does not accept 
liability for any damage inflicted by viewing the content of this email.