This message was deleted.
# general
s
This message was deleted.
a
Seems like linux issues
check the container to see which jars you have inside
I took the master branch and now I see this error: Readiness probe failed: Get “podIPAddress”: dial tcp podIPAddress80 connect: connection refused Warning Unhealthy 24s (x8 over 94s) kubelet Liveness probe failed: Get “podIPAddress”: dial tcp podIPAddress80 connect: connection refused
I see the issue, it’s because containerPort is now 8080 and readiness liveness is still on 80
I can create a quick PR to fix the readiness liveness issue if you wish
thankyou 1