By using AWS re:Post, you agree to the Terms of Use

EKS exec liveness and readiness probes


EKS "version": "1.21"

Exec liveness and readiness probes does not restart the pod

Name:         clockwork-57d74f6544-dsm8m
Namespace:    sandbox-cl-hc
Priority:     0
Start Time:   Fri, 29 Jul 2022 12:56:32 +0100
Labels:       app=clockwork
Annotations: eks.privileged
Status:       Running
Controlled By:  ReplicaSet/clockwork-57d74f6544
    State:          Running
      Started:      Fri, 29 Jul 2022 12:56:34 +0100
    Ready:          True
    Restart Count:  0
    Liveness:   exec [find /usr/src/app/tmp/alive] delay=30s timeout=1s period=15s #success=1 #failure=3
    Readiness:  exec [find /usr/src/app/tmp/alive] delay=30s timeout=1s period=15s #success=1 #failure=3

  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True

  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  17m                default-scheduler  Successfully assigned sandbox-cl-hc/clockwork-57d74f6544-dsm8m to
  Normal   Pulling    17m                kubelet            Pulling image ""
  Normal   Pulled     17m                kubelet            Successfully pulled image "" in 126.117763ms
  Normal   Created    17m                kubelet            Created container clockwork
  Normal   Started    17m                kubelet            Started container clockwork
  Warning  Unhealthy  16m (x2 over 16m)  kubelet            Liveness probe failed: find: /usr/src/app/tmp/alive: No such file or directory
  Warning  Unhealthy  16m (x2 over 16m)  kubelet            Readiness probe failed: find: /usr/src/app/tmp/alive: No such file or directory

The probes correctly identifies the pod as unhealthy but kubelet is not terminating the pod

restartPolicy is default Always

Does anyone have a clue as to why?

// Alexander

asked 18 days ago29 views
1 Answers


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.

Best regards,

answered 15 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions