Kubernetes Health Checks: Liveness vs. Readiness vs. Startup Probe

[@AntonPutra]

🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - [e-mail]

[@MuthaNagavamsi]

Very important concept, nicely explained. Thanks for sharing. I have a post scheduled on readiness probe tomorrow.

[@AntonPutra]

thanks!

[@bhomiktakhar8226]

As usual, great content ... relevant on my job and cloud in general, keep educating ..thank you.

[@AntonPutra]

Thanks for keeping coming back!

[@vishwasdhanwani6134]

Thanks for the simple & easy explanation. I'm still not clear with startup probe, startup probe will delay liveness & readiness check? instead can't we just increase delay for them

[@AntonPutra]

Well, with an initial delay, you can set a fixed time for warm-up, for example, 60 seconds. A startup probe allows you to start testing immediately, for example, every 10 seconds, with a high failure threshold value. So potentially, if your app is ready quicker than the fixed time, it's more efficient.

[@varunj34]

0:34, so if it only kills the container, and not the pod, I don't follow how it ends up getting redeployed on another node.

[@AntonPutra]

my bad, liveness probe will restart the container, it will not by default reschedule it on another node

[@varunj34]

@@AntonPutra Okay cool. just wanted to make sure I am not missing something. Thanks for replying!