Probe timing parameters (initialDelay, period, timeout) in Kubernetes - Step-by-Step Execution

Process Flow - Probe timing parameters (initialDelay, period, timeout)

Pod starts

↓

Wait initialDelay seconds

↓

Start first probe

↓

Probe runs with timeout

↓

Wait period seconds

↓

Repeat probe

↩Back to Probe runs with timeout

This flow shows how Kubernetes waits before starting probes, runs them with a timeout, then repeats them periodically.

Execution Sample

Kubernetes

livenessProbe:
  initialDelaySeconds: 5
  periodSeconds: 10
  timeoutSeconds: 3
  httpGet:
    path: /health
    port: 8080

Defines a liveness probe that waits 5 seconds before first check, runs every 10 seconds, and times out after 3 seconds.

Process Table

Step	Time (seconds)	Action	Probe State	Result
1	0	Pod starts	No probe yet	Waiting initialDelay
2	5	Initial delay ends	Start first probe	Probe sent
3	5-8	Probe running	Waiting for response	Success if response before 3s timeout
4	8	Probe finished	Probe success	Wait periodSeconds
5	18	Start next probe	Probe sent	Probe running
6	18-21	Probe running	Waiting for response	Success or failure
7	21	Probe finished	Probe success/failure	Wait periodSeconds
8	31	Start next probe	Probe sent	Repeat cycle
9	...	...	...	...
Exit	N/A	Pod stopped or probe failed	Probe stops	End of lifecycle or restart triggered

💡 Execution stops when pod stops or probe fails triggering restart

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	After Step 7	Final
Time (seconds)	0	5	8	18	21	N/A
Probe State	No probe	Running	Success	Running	Success/Failure	Stopped or Restarted

Key Moments - 3 Insights

Why does Kubernetes wait before starting the first probe?

Kubernetes waits for initialDelaySeconds (see Step 2) to give the container time to start before checking health.

What happens if the probe does not respond within timeoutSeconds?

If the probe times out (no response within timeoutSeconds during Steps 3 or 6), Kubernetes treats it as a failure.

How often does Kubernetes run the probe after the first check?

After the first probe, Kubernetes waits periodSeconds (see Steps 4 and 7) before running the next probe.

Visual Quiz - 3 Questions

Look at the execution table, at what time does the first probe start?

A 0 seconds

B 5 seconds

C 8 seconds

D 10 seconds

💡 Hint

Check Step 2 in the execution_table where initialDelay ends and first probe starts.

At which step does Kubernetes wait for the probe response with a timeout?

A Step 1

B Step 5

C Step 3

D Step 8

💡 Hint

Look at Step 3 where probe runs and waits for response within timeoutSeconds.

If periodSeconds is changed from 10 to 5, how does the timing in the table change?

A Probes run every 5 seconds instead of 10 seconds

B Initial delay changes to 5 seconds

C Timeout changes to 5 seconds

D Probe runs only once

💡 Hint

PeriodSeconds controls how often probes repeat after initialDelay (see Steps 4 and 7).

Concept Snapshot

Probe Timing Parameters in Kubernetes:
- initialDelaySeconds: wait before first probe
- periodSeconds: interval between probes
- timeoutSeconds: max wait for probe response
Probes start after initialDelay, run with timeout, then repeat every periodSeconds.

Full Transcript

In Kubernetes, probes check container health. The initialDelaySeconds tells Kubernetes to wait before starting the first probe, allowing the container to initialize. After this delay, Kubernetes sends the probe and waits up to timeoutSeconds for a response. If the probe succeeds, Kubernetes waits periodSeconds before sending the next probe. This cycle repeats until the pod stops or a probe fails, which may trigger a restart. Understanding these timing parameters helps ensure probes run at the right times without false failures.

Practice

1. What does the initialDelaySeconds parameter control in a Kubernetes probe?

easy

A. The time to wait before the first probe check starts

B. The maximum time to wait for a probe response

C. The frequency of probe checks after the first one

D. The number of retries before marking the pod as failed

Solution

1. Step 1: Understand the role of initialDelaySeconds

   This parameter sets how long Kubernetes waits before performing the first probe check on a container.

2. Step 2: Differentiate from other timing parameters

   timeoutSeconds limits wait time per check, and periodSeconds sets how often checks repeat after the first.

3. Final Answer:

   The time to wait before the first probe check starts -> Option A

4. Quick Check:

   initialDelaySeconds = wait before first check [OK]

Hint: initialDelaySeconds delays first check only [OK]

Common Mistakes:

• Confusing initialDelaySeconds with timeoutSeconds
• Thinking it controls check frequency
• Assuming it sets retry count

2. Which of the following is the correct syntax to set a liveness probe with initialDelaySeconds of 10, periodSeconds of 5, and timeoutSeconds of 2 in a pod spec?

easy

A. livenessProbe:
initialDelaySeconds: '10'
periodSeconds: '5'
timeoutSeconds: '2'

B. livenessProbe:
initialDelaySeconds: 10
periodSeconds: 5
timeoutSeconds: 2

C. livenessProbe:
initialDelay: 10
period: 5
timeout: 2

D. livenessProbe:
delayInitialSeconds: 10
periodSeconds: 5
timeoutSeconds: 2

Solution

1. Step 1: Check correct parameter names

   The correct keys are initialDelaySeconds, periodSeconds, and timeoutSeconds exactly as spelled.

2. Step 2: Validate value types and syntax

   Values should be integers without quotes. livenessProbe: initialDelaySeconds: 10 periodSeconds: 5 timeoutSeconds: 2 uses correct keys and integer values.

3. Final Answer:

   Correct YAML with proper keys and integer values -> Option B

4. Quick Check:

   Use exact keys and integer values [OK]

Hint: Use exact parameter names with integer values [OK]

Common Mistakes:

• Misspelling parameter names
• Using quotes around numbers
• Using incorrect keys like 'delayInitialSeconds'

3. Given this liveness probe configuration:

livenessProbe:
  initialDelaySeconds: 5
  periodSeconds: 10
  timeoutSeconds: 3

If the container starts at time 0, when will the first probe timeout occur if the probe command does not respond?

medium

A. At 15 seconds

B. At 5 seconds

C. At 10 seconds

D. At 8 seconds

Solution

1. Step 1: Calculate when first probe starts

   The first probe starts after initialDelaySeconds, so at 5 seconds.

2. Step 2: Add timeoutSeconds to find timeout moment

   The probe waits up to timeoutSeconds (3 seconds) for a response, so timeout occurs at 5 + 3 = 8 seconds.

3. Final Answer:

   At 8 seconds -> Option D

4. Quick Check:

   initialDelay + timeout = 8 seconds [OK]

Hint: Add initialDelaySeconds and timeoutSeconds for first timeout [OK]

Common Mistakes:

• Using periodSeconds instead of timeoutSeconds for timeout
• Forgetting to add initialDelaySeconds
• Assuming timeout happens at periodSeconds

4. You configured a readiness probe with initialDelaySeconds: 0, periodSeconds: 2, and timeoutSeconds: 5. The probe command hangs and never returns. What is the likely problem?

medium

A. initialDelaySeconds cannot be zero

B. periodSeconds must be greater than timeoutSeconds

C. timeoutSeconds is longer than periodSeconds, causing overlapping probes

D. timeoutSeconds must be less than 1 second

Solution

1. Step 1: Analyze timing relationship

   The probe runs every 2 seconds (periodSeconds) but waits up to 5 seconds (timeoutSeconds) for a response.

2. Step 2: Identify overlapping probes issue

   Since timeout is longer than period, new probes start before previous finish, causing overlap and possible resource issues.

3. Final Answer:

   timeoutSeconds is longer than periodSeconds, causing overlapping probes -> Option C

4. Quick Check:

   timeoutSeconds > periodSeconds causes overlap [OK]

Hint: timeoutSeconds should be less than or equal to periodSeconds [OK]

Common Mistakes:

• Thinking initialDelaySeconds cannot be zero
• Assuming timeoutSeconds must be less than 1
• Ignoring probe overlap effects

5. You want a startup probe to check a container's readiness only after 30 seconds, then check every 10 seconds, with each check timing out after 4 seconds. Which configuration correctly sets these parameters?

hard

A. startupProbe:
initialDelaySeconds: 30
periodSeconds: 10
timeoutSeconds: 4

B. startupProbe:
initialDelaySeconds: 10
periodSeconds: 30
timeoutSeconds: 4

C. startupProbe:
initialDelaySeconds: 30
periodSeconds: 4
timeoutSeconds: 10

D. startupProbe:
initialDelaySeconds: 4
periodSeconds: 10
timeoutSeconds: 30

Solution

1. Step 1: Match each parameter to requirement

   initialDelaySeconds should be 30 to delay first check, periodSeconds 10 for check frequency, and timeoutSeconds 4 for max wait per check.

2. Step 2: Verify option correctness

   startupProbe: initialDelaySeconds: 30 periodSeconds: 10 timeoutSeconds: 4 matches all requirements exactly; others mix values incorrectly.

3. Final Answer:

   startupProbe with initialDelaySeconds 30, periodSeconds 10, timeoutSeconds 4 -> Option A

4. Quick Check:

   Match timing values to parameters exactly [OK]

Hint: Match each timing value to correct parameter name [OK]

Common Mistakes:

• Swapping periodSeconds and timeoutSeconds values
• Setting initialDelaySeconds too low
• Confusing startupProbe with livenessProbe