You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I'm not sure if I'm missing something here. I've deployed the docker container to kubernetes.
Almost everything works, expect when I look at the logs of the pod, I see several lines in the logs caused by the livenessprobe. [info] 17#17: *177 client closed connection while waiting for request, client: 192.168.1.1, server: 0.0.0.0:8000.
I've changed the livenessprobe to from httpGet to tcpSocket, but still having the same problem.
Is there another path I have to check for liveness probe? or is there another env variable I need to set?
The text was updated successfully, but these errors were encountered:
❓ Question
Hi I'm not sure if I'm missing something here. I've deployed the docker container to kubernetes.
Almost everything works, expect when I look at the logs of the pod, I see several lines in the logs caused by the livenessprobe.
[info] 17#17: *177 client closed connection while waiting for request, client: 192.168.1.1, server: 0.0.0.0:8000
.I've changed the livenessprobe to from httpGet to tcpSocket, but still having the same problem.
Is there another path I have to check for liveness probe? or is there another env variable I need to set?
The text was updated successfully, but these errors were encountered: