Startup allows initialization, readiness controls traffic eligibility and liveness can trigger restarts. Each probe answers a different operational question.
Before you start
You should understand Pods, Deployments and Services. Read desired configuration separately from observed cluster state. Use a development cluster when trying changes, and inspect events and status rather than assuming that an accepted manifest means the workload is ready to serve traffic.
The practical goal is to reason through this situation: A slow-starting service uses startup allowance before ordinary liveness checks. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Allow startup time
Initialization can need a different tolerance from a running process.
Step 2: Define traffic readiness
Only route useful work to instances ready to handle it.
Step 3: Keep restart criteria focused
Shared dependency failures should not automatically produce restart storms.
Worked scenario
A slow-starting service uses startup allowance before ordinary liveness checks.
A database outage makes account requests impossible, so readiness can withdraw traffic. The application process remains responsive and able to reconnect; liveness need not restart it. During slow initialization, startup allowance prevents premature liveness failures before the process has had a reasonable chance to become operational.
Common mistake
A database outage should not automatically cause every application instance to restart.
Verify the behavior
Test slow start, outage, recovery and draining separately.
Interview exercise
Define useful probes.
Answer and reasoning
Keep liveness focused on local recoverability and readiness on safe traffic handling; test both dependency outage and shutdown.
Continue learning
Compare the scenario with the Kubernetes interview questions and test your understanding with the Kubernetes MCQs. For terminology and implementation details, consult the reference material.