Skip to content

Health probes fail out of the blue on existing installation

While debugging stackspin#1292 (closed) I noticed that out of the blue, both Liveness probe and Readiness probe failed for an existing, running NC instance on my varac-test cluster:

Warning  Unhealthy  25h                   kubelet            Startup probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)     
Warning  Unhealthy  5m5s (x32 over 25h)   kubelet            Liveness probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)    
Warning  Unhealthy  2m55s (x41 over 25h)  kubelet            Readiness probe failed: Get "http://10.42.0.242:80/status.php": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

We might want to relac the timeouts a bit.

Edited by Varac
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information