Lightning Talk: Slow Starting Containers, How to Check Their Health?
summary
Kubernetes liveness probes cause restart loops for slow-starting Java servers when default initialDelaySeconds and failureThreshold are too short, and increasing delays hides crashes or slows deadlock recovery. A proposed concrete fix adds a third starter probe that keeps readiness/liveness checks disabled until startup completes; it’s specified as KEP (CAP 950) sponsored by SIG Node after months of community iteration and targets inclusion in the next Kubernetes release.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:18Container probes bifecta
- 2:04Long initialDelay Seconds: second start + deadlock
- 3:08Strategies overview
- 3:26Container probes trifecta
related talks
26mKubernetes Probes: What are they for and why you should always properly configure them
33mPID 1, SIG Handling, Hooks & Probes: Managing Container Lifecycle Correctly
45mTroubleshooting containerized applications
08m⚡ Fast Restarts, Not Just Fast Starts: Accelerating Pod Recovery
10mLightning Talk
30mAfterlife tales: Troubleshooting containerized applications
37mSelf-Healing Applications with Docker and Kubernetes
26mWait! Can Your Pod Survive a Restart?
