Probe timing parameters (initialDelay, period, timeout) in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the initial delay for a liveness probe to 10 seconds.

Kubernetes

livenessProbe:
  initialDelaySeconds: [1]

Drag options to blanks, or click blank then click option'

A10

B15

C20

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero or too low value causing premature probe failures.

The initialDelaySeconds sets how long Kubernetes waits before starting the probe. Here, it is set to 10 seconds.

2fill in blank

medium

Complete the code to set the probe period to 5 seconds.

Kubernetes

readinessProbe:
  periodSeconds: [1]

Drag options to blanks, or click blank then click option'

A3

B5

C10

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Setting periodSeconds too low causing unnecessary load.

The periodSeconds defines how often the probe runs. Setting it to 5 means the probe runs every 5 seconds.

3fill in blank

hard

Fix the error in the probe timeout setting to 3 seconds.

Kubernetes

startupProbe:
  timeoutSeconds: [1]

Drag options to blanks, or click blank then click option'

A5

B2

C1

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Setting timeoutSeconds too low causing probe failures.

The timeoutSeconds defines how long to wait for the probe to respond. Setting it to 3 seconds means the probe must respond within 3 seconds.

4fill in blank

hard

Fill both blanks to set initial delay to 15 seconds and period to 10 seconds for a liveness probe.

Kubernetes

livenessProbe:
  initialDelaySeconds: [1]
  periodSeconds: [2]

Drag options to blanks, or click blank then click option'

A15

B5

C10

D20

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up initialDelaySeconds and periodSeconds values.

Here, initialDelaySeconds is set to 15 seconds to wait before starting probes, and periodSeconds is set to 10 seconds to run probes every 10 seconds.

5fill in blank

hard

Fill all three blanks to set startup probe with initial delay 20, period 5, and timeout 4 seconds.

Kubernetes

startupProbe:
  initialDelaySeconds: [1]
  periodSeconds: [2]
  timeoutSeconds: [3]

Drag options to blanks, or click blank then click option'

A20

B5

C4

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Setting timeoutSeconds longer than periodSeconds.

The startup probe waits 20 seconds before starting, runs every 5 seconds, and times out after 4 seconds if no response.

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