A web Pod for a tax-filing helper fails its liveness probe and restarts in a loop, yet the process is only slow to finish initializing. What probe change best stops premature kills?
Select an answer to reveal the explanation.
Short Explanation
Slow starters need a warmup lap before the referee starts calling fouls. A startupProbe gives the app time to initialize; liveness stays quiet until startup succeeds. That stops the restart loop caused by checking too early.
Full Explanation
startupProbe is designed for containers with long initialization. While the startupProbe is failing, liveness and readiness probes are disabled, preventing kubelet from killing a container that is still starting. Once startup succeeds, normal liveness and readiness take over. Removing all probes hides failures; probing an unrelated always-open port defeats the purpose; tightening liveness makes the restart loop worse.