For a containerized application that requires a long initialization time, why is it recommended to use a startupProbe instead of relying solely on a livenessProbe?
hard📝 Conceptual Q10 of 15
Kubernetes - Health Checks and Probes
For a containerized application that requires a long initialization time, why is it recommended to use a startupProbe instead of relying solely on a livenessProbe?
ABecause livenessProbe cannot detect container crashes after startup
BBecause startupProbe prevents premature restarts during the startup phase by allowing longer failure thresholds
CBecause startupProbe continuously monitors resource usage during runtime
DBecause livenessProbe is deprecated in favor of startupProbe
Step-by-Step Solution
Solution:
Step 1: Understand startupProbe role
It allows Kubernetes to wait longer during container startup before considering it unhealthy.
Step 2: Compare with livenessProbe
LivenessProbe checks ongoing health and may restart container prematurely if app is slow to start.
Step 3: Conclusion
Using startupProbe avoids unnecessary restarts during long initialization.
Final Answer:
Because startupProbe prevents premature restarts during the startup phase by allowing longer failure thresholds -> Option B
