1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
The readiness probe is not responsible for restarting a pod:
- Define readiness probes
- Types of probe Readiness probe will cause the removal of pod IP address from the endpoints of all services that match the pod.
According to the description of your pod, it is ready and running. The events say that the liveness probe failed twice. In the same description, the livness probe has to fail 3 consecutive times to trigger the failure of the liveness probe, which is not the case in the events.
Try to adapt failureThreshold and periodSeconds (Configure Probes) based on your application to get the right behavior you expect from readiness and liveness probes.
Best regards,
answered 2 years ago
Relevant content
- asked 5 months ago
- asked 4 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago