Solution

Mon, 01 Jan 0001 00:00:00 +0000

Observe the behavior of the pod you will notice the pod is automatically restarted after a few tens of seconds:

$ kubectl get po -w
NAME READY STATUS RESTARTS AGE
demo 1/1 Running 0 2s
demo 1/1 Running 1 (1s ago) 76s

Going a little deeper in the details, we understand this is due to the liveness probe failing:

$ kubectl describe po demo
...
Events:
 Type Reason Age From Message
 ---- ------ ---- ---- -------
 Normal Scheduled 2m8s default-scheduler Successfully assigned default/demo to worker1
 Normal Pulled 2m7s kubelet Successfully pulled image "k8s.gcr.io/busybox" in 578.053377ms
 Normal Pulling 53s (x2 over 2m7s) kubelet Pulling image "k8s.gcr.io/busybox"
 Normal Created 52s (x2 over 2m6s) kubelet Created container busybox
 Normal Started 52s (x2 over 2m6s) kubelet Started container busybox
 Normal Pulled 52s kubelet Successfully pulled image "k8s.gcr.io/busybox" in 512.064103ms
 Warning Unhealthy 8s (x6 over 93s) kubelet Liveness probe failed: cat: can't open '/tmp/healthy': No such file or directory
 Normal Killing 8s (x2 over 83s) kubelet Container busybox failed liveness probe, will be restarted

If we check the pod’s specification, we can see the liveness probe checks the existence of a file:

Challenge 7 on Exoscale Academy

Solution