"Liveliness and Readiness probes" are faling and returning statuscode 503 in Kubernetes
I'm seeing liveliness and readiness probes failing in the Kubernetes setup.
Below im attaching screenshots of Pod Events, Resource Limits of the pod, probe configurations.
Anyone can help he with this issue and some explanation why this can happen and when do we see status code 503 in probes.
thankyou in advance!
Below screen shot is from events section of pod
Configurations of liveliness and readiness probe
Resource limits of pod
FYI: I've tried changing initialDelaySeconds to 180 didn't help and also i don't see any issue with service startup it is not taking much time to start I could see in logs of pod.
Similar Questions
1 Answer
Community wiki answer for better visibility. As ni_kill12 has mentioned in the comment, the issue is solved:
I got the issue, what is happening is one of the component is going OUT_OF_STATE because of that readiness and liveliness probe is failing for me. I got to know about this by hitting the request of livelines probe. This link helped me to understand probes.