Startup probe concept in Kubernetes - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a startup probe using an HTTP GET request.

Kubernetes

startupProbe:
  httpGet:
    path: [1]
    port: 8080

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

A/healthz

B/status

C/ready

D/check

Attempts:

3 left

💡 Hint

Common Mistakes

Using a path without a leading slash

Using an unrelated path like /status

The /healthz path is commonly used for health checks including startup probes.

2fill in blank

medium

Complete the code to set the initial delay seconds for the startup probe.

Kubernetes

startupProbe:
  initialDelaySeconds: [1]

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

A0

B30

C10

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting it to 0 which may cause immediate failure

Setting too high causing slow startup detection

initialDelaySeconds defines how long to wait before starting the probe. 10 seconds is a common safe value.

3fill in blank

hard

Fix the error in the startup probe configuration by completing the missing field.

Kubernetes

startupProbe:
  tcpSocket:
    port: [1]

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

Ahttp

Bport

C80

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a number

Using an invalid port name

The port field must be a number or named port. 8080 is a common port for HTTP services.

4fill in blank

hard

Fill both blanks to configure a startup probe with an exec command and failure threshold.

Kubernetes

startupProbe:
  exec:
    command:
      - [1]
      - [2]
  failureThreshold: 5

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

Acat

Bls

C/tmp/startup-ready

D/bin/check-startup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'ls' which lists directory contents

Using an invalid file path

The exec command runs cat /tmp/startup-ready to check if the file exists, indicating startup completion.

5fill in blank

hard

Fill all three blanks to create a startup probe with HTTP GET, timeout, and period seconds.

Kubernetes

startupProbe:
  httpGet:
    path: [1]
    port: [2]
  timeoutSeconds: [3]
  periodSeconds: 10

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

A/startup

B8080

C5

D/healthz

Attempts:

3 left

💡 Hint

Common Mistakes

Using a path that is not a health check

Setting timeoutSeconds higher than periodSeconds

The probe uses /healthz path on port 8080 with a 5 second timeout for responsiveness.

Practice

1. What is the main purpose of a startupProbe in Kubernetes?

easy

A. To monitor CPU and memory usage of the pod

B. To restart the pod immediately when it crashes

C. To check if the application has started before other health checks run

D. To manage network traffic routing to the pod

Solution

1. Step 1: Understand the role of startupProbe

   The startupProbe is designed to check if an application has started successfully before Kubernetes runs readiness or liveness probes.

2. Step 2: Differentiate from other probes

   Unlike liveness or readiness probes, startupProbe prevents Kubernetes from killing pods that take longer to start.

3. Final Answer:

   To check if the application has started before other health checks run -> Option C

4. Quick Check:

   startupProbe checks app start status = A [OK]

Hint: Startup probe delays other checks until app starts [OK]

Common Mistakes:

• Confusing startupProbe with livenessProbe
• Thinking startupProbe manages resource usage
• Assuming startupProbe handles traffic routing

2. Which of the following is the correct syntax to define a startupProbe using an HTTP GET request in a pod spec?

easy

A. startupProbe:
exec:
command: ["curl", "-f", "http://localhost:8080/healthz"]
timeoutSeconds: 5

B. startupProbe:
httpGet:
path: /healthz
port: 8080
failureThreshold: 30
periodSeconds: 10

C. startupProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 5

D. startupProbe:
httpGet:
path: /status
port: 80
successThreshold: 3

Solution

1. Step 1: Identify correct HTTP GET syntax for startupProbe

   The startupProbe uses httpGet with path and port fields, plus timing settings like failureThreshold and periodSeconds.

2. Step 2: Compare options for correctness

   startupProbe: httpGet: path: /healthz port: 8080 failureThreshold: 30 periodSeconds: 10 correctly uses httpGet with path /healthz, port 8080, and timing fields. Other options use exec or tcpSocket or wrong ports/fields.

3. Final Answer:

   startupProbe: httpGet: path: /healthz port: 8080 failureThreshold: 30 periodSeconds: 10 -> Option B

4. Quick Check:

   startupProbe HTTP GET with path and port = A [OK]

Hint: HTTP GET startupProbe needs path, port, failureThreshold [OK]

Common Mistakes:

• Using exec probe syntax instead of httpGet
• Missing failureThreshold or periodSeconds
• Incorrect port or path values

3. Given this pod spec snippet, what will happen if the startupProbe fails repeatedly during startup?

startupProbe:
  httpGet:
    path: /start
    port: 8080
  failureThreshold: 5
  periodSeconds: 2
livenessProbe:
  httpGet:
    path: /live
    port: 8080
  initialDelaySeconds: 10
  periodSeconds: 5

medium

A. Kubernetes will never restart the pod because startupProbe is ignored

B. Kubernetes will restart the pod after 10 seconds of livenessProbe failures

C. Kubernetes will restart the pod after 10 seconds of readinessProbe failures

D. Kubernetes will restart the pod after 10 seconds of startupProbe failures

Solution

1. Step 1: Calculate startupProbe failure timeout

   failureThreshold 5 and periodSeconds 2 means Kubernetes waits 5*2=10 seconds of failed startupProbe checks before restarting.

2. Step 2: Understand probe precedence during startup

   During startup, startupProbe controls pod health. LivenessProbe starts after startupProbe succeeds, so restart depends on startupProbe failures first.

3. Final Answer:

   Kubernetes will restart the pod after 10 seconds of startupProbe failures -> Option D

4. Quick Check:

   startupProbe failureThreshold * periodSeconds = restart delay [OK]

Hint: Restart delay = failureThreshold x periodSeconds of startupProbe [OK]

Common Mistakes:

• Confusing startupProbe failure timing with livenessProbe
• Assuming readinessProbe triggers restart
• Ignoring startupProbe during pod startup

4. You configured a startupProbe but your pod keeps restarting immediately. Which fix is most likely correct?

medium

A. Increase failureThreshold and periodSeconds to allow more startup time

B. Remove the startupProbe to rely only on livenessProbe

C. Change the startupProbe to a readinessProbe

D. Set initialDelaySeconds to 0 in the livenessProbe

Solution

1. Step 1: Identify cause of immediate restarts

   If the startupProbe fails too quickly, Kubernetes restarts the pod before it finishes starting.

2. Step 2: Adjust startupProbe timing

   Increasing failureThreshold and periodSeconds gives the app more time to start before Kubernetes kills it.

3. Final Answer:

   Increase failureThreshold and periodSeconds to allow more startup time -> Option A

4. Quick Check:

   Longer startupProbe timeout prevents premature restarts [OK]

Hint: Longer failureThreshold and periodSeconds prevent early restarts [OK]

Common Mistakes:

• Removing startupProbe loses slow start protection
• Confusing startupProbe with readinessProbe
• Setting initialDelaySeconds on livenessProbe doesn't fix startup timing

5. You have a slow-starting app that takes about 3 minutes to initialize. How should you configure the startupProbe to avoid premature pod restarts?

hard

A. Set failureThreshold to 18 and periodSeconds to 10

B. Set failureThreshold to 3 and periodSeconds to 30

C. Set failureThreshold to 1 and periodSeconds to 100

D. Disable startupProbe and rely on livenessProbe with initialDelaySeconds 180

Solution

1. Step 1: Calculate total startupProbe timeout needed

   App needs 3 minutes (180 seconds) to start. Total timeout = failureThreshold x periodSeconds.

2. Step 2: Choose values matching 180 seconds

   Set failureThreshold to 18 and periodSeconds to 10: 18 x 10 = 180 seconds, allowing full startup time before restart.

3. Step 3: Evaluate other options

   Set failureThreshold to 1 and periodSeconds to 100: failureThreshold to 1 and periodSeconds to 100 = 100 seconds (too short). Set failureThreshold to 3 and periodSeconds to 30: 3 x 30 = 90 seconds (too short). Disable startupProbe and rely on livenessProbe with initialDelaySeconds 180 disables startupProbe, risking premature restarts from livenessProbe.

4. Final Answer:

   Set failureThreshold to 18 and periodSeconds to 10 -> Option A

5. Quick Check:

   failureThreshold x periodSeconds = startup timeout [OK]

Hint: Multiply failureThreshold by periodSeconds to match startup time [OK]

Common Mistakes:

• Configuring insufficient total timeout (failureThreshold x periodSeconds < 180s)
• Disabling startupProbe causing premature restarts
• Setting only initialDelaySeconds without startupProbe