When a readiness Probe failed, kubernetes remove the Pod from the service point so that traffic could not move toward that pod. Pod remain in the node. Kubernetes continues to run the readiness probe checks against the container. If the application recovers and the readiness probe passes again, Kubernetes automatically re-adds the pod to the service endpoints to resume traffic.
If the pod remain failed in readiness probe, it is of no use in and only consuming the Node CPU and memory. Then why kubernetes do not kill the pod and remove it from the Node? Why there is no time frame to check the readiness probe failure after which the Pod should be removed from the node?
Hello Qazaidi,
If you’d like your container to be killed and restarted if a probe fails, then specify a liveness probe, and specify a restartPolicy of Always or OnFailure
The liveness probe passes when the app itself is healthy, but the readiness probe additionally checks that each required back-end service is available. This helps you avoid directing traffic to Pods that can only respond with error messages.
WHY?
If you want to notice the difference between an app that has failed and an app that is still processing its startup data, you might prefer a readiness probe.
Thanks,
Manan