Kubernetes Health Checks: Liveness vs. Readiness vs. Startup Probe
ฝัง
- เผยแพร่เมื่อ 28 มิ.ย. 2024
- 🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
▬▬▬▬▬ Experience & Location 💼 ▬▬▬▬▬
► I’m a Senior Software Engineer at Juniper Networks (12+ years of experience)
► Located in San Francisco Bay Area, CA (US citizen)
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
► LinkedIn: / anton-putra
► Twitter/X: / antonvputra
► GitHub: github.com/antonputra
► Email: me@antonputra.com
▬▬▬▬▬▬ Related videos 👨🏫 ▬▬▬▬▬▬
👉 [Playlist] Kubernetes Tutorials: • Kubernetes Tutorials
👉 [Playlist] Terraform Tutorials: • Terraform Tutorials fo...
👉 [Playlist] Network Tutorials: • Network Tutorials
👉 [Playlist] Apache Kafka Tutorials: • Apache Kafka Tutorials
👉 [Playlist] Performance Benchmarks: • Performance Benchmarks
👉 [Playlist] Database Tutorials: • Database Tutorials
▬▬▬▬▬▬▬ Timestamps ⏰ ▬▬▬▬▬▬▬
0:00 Intro
0:18 Liveness Probe
1:11 Readiness Probe
1:50 Startup Probe
▬▬▬▬▬▬▬ Source Code 📚 ▬▬▬▬▬▬▬
► GitHub: github.com/antonputra/tutoria...
#kubernetes #docker #devops - วิทยาศาสตร์และเทคโนโลยี
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
As usual, great content ... relevant on my job and cloud in general, keep educating ..thank you.
Thanks for keeping coming back!
Very important concept, nicely explained. Thanks for sharing.
I have a post scheduled on readiness probe tomorrow.
thanks!
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
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.
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.
my bad, liveness probe will restart the container, it will not by default reschedule it on another node
@@AntonPutra Okay cool. just wanted to make sure I am not missing something. Thanks for replying!