Startup probe concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Startup Probe in Kubernetes

What is the main purpose of a startup probe in a Kubernetes pod?

A To check if the application inside the container has started successfully before other probes run

B To continuously monitor the CPU usage of the container

C To restart the pod immediately when the container crashes

D To manage network traffic routing to the pod

💡 Hint

Think about what happens when an app takes time to start and how Kubernetes knows when to begin health checks.

The startup probe is used to determine if the application inside the container has started. It prevents Kubernetes from killing the pod prematurely by delaying liveness and readiness probes until the app is ready.

💻 Command Output

intermediate

Startup Probe Failure Behavior

Given this startup probe configuration, what will happen if the probe fails continuously?

startupProbe:
  exec:
    command:
    - cat
    - /tmp/healthy
  failureThreshold: 3
  periodSeconds: 5

A The container will be restarted immediately after the first failure

B The container will be restarted after 3 seconds of continuous failure

C The container will never restart regardless of failures

D The container will be restarted after 15 seconds of continuous failure

💡 Hint

Calculate failureThreshold multiplied by periodSeconds to find the restart delay.

The failureThreshold of 3 and periodSeconds of 5 means Kubernetes waits 3 failures spaced 5 seconds apart (total 15 seconds) before restarting the container.

❓ Configuration

advanced

Correct Startup Probe YAML Configuration

Which of the following YAML snippets correctly configures a startup probe that checks HTTP path /healthz on port 8080 every 10 seconds, with a failure threshold of 5?

A

startupProbe:
  httpGet:
    path: /healthz
    port: 8080
  periodSeconds: 10
  failureThreshold: 5

B

startupProbe:
  httpGet:
    path: /healthz
    port: 8080
  periodSeconds: 5
  failureThreshold: 10

C

startupProbe:
  exec:
    command:
    - curl
    - http://localhost:8080/healthz
  periodSeconds: 10
  failureThreshold: 5

D

startupProbe:
  tcpSocket:
    port: 8080
  periodSeconds: 10
  failureThreshold: 5

💡 Hint

Look for the correct probe type and matching period and failureThreshold values.

Option A uses httpGet with the correct path, port, periodSeconds, and failureThreshold as requested. Option A swaps period and threshold. Option A uses exec with curl which is not recommended. Option A uses tcpSocket which does not check HTTP path.

❓ Troubleshoot

advanced

Diagnosing Startup Probe Failures

A pod with a startup probe keeps restarting even though the application eventually starts. What is the most likely cause?

A The readiness probe is misconfigured and causing restarts

B The pod has insufficient CPU resources causing slow startup

C The startup probe command or HTTP path is incorrect, causing probe failures

D The container image is missing required environment variables

💡 Hint

Check the probe configuration carefully for correctness.

If the startup probe is misconfigured (wrong command or path), it will fail repeatedly causing Kubernetes to restart the pod even if the app starts later.

✅ Best Practice

expert

Best Practice for Using Startup Probe with Slow-Starting Apps

For an application that takes a long time to start, what is the best practice when configuring probes in Kubernetes?

A Set very short liveness probe intervals to detect failures quickly

B Use a startup probe to delay liveness and readiness probes until the app is ready, preventing premature restarts

C Disable readiness probes to avoid blocking traffic

D Use only readiness probes and no startup or liveness probes

💡 Hint

Think about how Kubernetes decides when to start health checks and restart containers.

Startup probes are designed to handle slow-starting apps by delaying liveness and readiness probes until the app is confirmed started, avoiding unnecessary restarts.