The readiness probe is not responsible for restarting a pod:
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.
Scanner and Probes not activatedasked 5 months ago
Codebuild, EKS and private pypi serverasked a month ago
EKS Anywhere\Connector - Register New Cluster Button Does Not Reactasked 5 months ago
AWS Managed Active Directory - Disk error and restart capabilityasked a month ago
EKS - antivirus and best practicesasked 2 years ago
EKS exec liveness and readiness probesasked 18 days ago
Does DMS drop and creates the target files in S3 target endpoints?asked 24 days ago
EC2 RebootInstances performs dirty restartasked 5 months ago
Amplify Studio questions on workload and production readinessasked 7 months ago
NLB-ECS Health CheckAccepted Answerasked 2 years ago