One of our application service pods is getting restarted and the Last cause specified is "Error" due to 143 error code.

There are no errors shown in the last hundred lines of the previous container logs. The only error reference is the Readiness probe entry in the pod's description. However based in all the references I have seen in my searches state that failures in the readiness probe should only be preventing the routing of traffic to the pod instance. Is there a scenario wherein repeated readiness probe failures will cause the Kubernetes pod to be marked unhealthy and be restarted?