HTTP probe configuration in Kubernetes - Time & Space Complexity

Time Complexity: HTTP probe configuration

O(n)

Understanding Time Complexity

When Kubernetes checks if an app is healthy using HTTP probes, it sends requests repeatedly.

We want to understand how the number of these checks grows as the app or cluster size changes.

Scenario Under Consideration

Analyze the time complexity of the following HTTP readiness probe configuration.

readinessProbe:
  httpGet:
    path: /healthz
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10
  failureThreshold: 3

This config tells Kubernetes to send an HTTP GET request to /healthz on port 8080 every 10 seconds after waiting 5 seconds initially, and to consider the pod unhealthy after 3 failures.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Kubernetes sends HTTP GET requests repeatedly to check pod health.
• How many times: Every 10 seconds indefinitely until pod stops or fails.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10 pods	10 probes every 10 seconds
100 pods	100 probes every 10 seconds
1000 pods	1000 probes every 10 seconds

Pattern observation: The number of HTTP probe requests grows linearly with the number of pods.

Final Time Complexity

Time Complexity: O(n)

This means the total number of health check requests grows directly in proportion to the number of pods.

Common Mistake

[X] Wrong: "The probe runs only once per pod, so it doesn't add up much."

[OK] Correct: The probe runs repeatedly at fixed intervals, so the total checks increase as pods increase and time passes.

Interview Connect

Understanding how repeated health checks scale helps you design efficient monitoring in real systems.

Self-Check

"What if the periodSeconds is halved? How would the time complexity change?"

Practice

1. What is the main purpose of an HTTP probe in Kubernetes?

easy

A. To deploy new versions of the application automatically

B. To store application logs for debugging

C. To check if the application is running and responding to HTTP requests

D. To manage network traffic between pods

Solution

1. Step 1: Understand the role of HTTP probes

   HTTP probes send HTTP requests to the app to check if it is alive and ready.

2. Step 2: Identify the correct purpose

   Only To check if the application is running and responding to HTTP requests describes checking app health via HTTP requests.

3. Final Answer:

   To check if the application is running and responding to HTTP requests -> Option C

4. Quick Check:

   HTTP probe purpose = health check [OK]

Hint: HTTP probes test app health by sending HTTP requests [OK]

Common Mistakes:

• Confusing probes with deployment or logging
• Thinking probes manage network traffic
• Assuming probes store logs

2. Which of the following is the correct syntax to define an HTTP liveness probe in a Kubernetes pod spec?

easy

A. livenessProbe:
exec:
command: ["curl", "/healthz"]
initialDelaySeconds: 5
periodSeconds: 10

B. livenessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 5
periodSeconds: 10

C. livenessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 5
periodSeconds: 10

D. livenessProbe:
httpGet:
url: http://localhost:8080/healthz
initialDelaySeconds: 5
periodSeconds: 10

Solution

1. Step 1: Review HTTP probe syntax

   The correct HTTP probe uses httpGet with path and port keys.

2. Step 2: Identify the correct YAML structure

   livenessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 periodSeconds: 10 correctly uses httpGet with path and port. livenessProbe: httpGet: url: http://localhost:8080/healthz initialDelaySeconds: 5 periodSeconds: 10 is invalid because url is not a valid key.

3. Final Answer:

   Correct HTTP liveness probe syntax with httpGet, path, and port -> Option B

4. Quick Check:

   httpGet uses path and port keys [OK]

Hint: Use httpGet with path and port, not url [OK]

Common Mistakes:

• Using 'url' instead of 'path' in httpGet
• Confusing exec or tcpSocket probes with httpGet
• Wrong indentation or missing keys

3. Given this probe configuration snippet in a pod spec:

livenessProbe:
  httpGet:
    path: /status
    port: 8080
  initialDelaySeconds: 10
  periodSeconds: 5

What will Kubernetes do after the pod starts?

medium

A. Send an HTTP GET to /status only once after 10 seconds

B. Send an HTTP GET to /status immediately, then every 10 seconds

C. Wait 5 seconds, then send an HTTP GET to /status every 10 seconds

D. Wait 10 seconds, then send an HTTP GET to /status every 5 seconds

Solution

1. Step 1: Understand initialDelaySeconds

   This value tells Kubernetes to wait 10 seconds after pod start before first probe.

2. Step 2: Understand periodSeconds

   This value sets the interval between probes, here every 5 seconds.

3. Final Answer:

   Wait 10 seconds, then send an HTTP GET to /status every 5 seconds -> Option D

4. Quick Check:

   initialDelaySeconds = wait, periodSeconds = repeat interval [OK]

Hint: initialDelaySeconds = wait before first probe, periodSeconds = probe interval [OK]

Common Mistakes:

• Confusing initialDelaySeconds with periodSeconds
• Assuming immediate probe on pod start
• Mixing up timing values

4. You configured this HTTP readiness probe:

readinessProbe:
  httpGet:
    path: /ready
    port: 80
  initialDelaySeconds: 5
  periodSeconds: 10
  timeoutSeconds: 2

But Kubernetes marks the pod as not ready even though the app is healthy. What is the likely problem?

medium

A. The probe path /ready is incorrect or not handled by the app

B. initialDelaySeconds is too high, delaying readiness

C. timeoutSeconds is too long, causing probe to fail

D. periodSeconds is too short, causing probe overload

Solution

1. Step 1: Check probe path correctness

   If the app does not respond correctly to /ready, probe fails and pod is not ready.

2. Step 2: Evaluate timing parameters

   initialDelaySeconds of 5 is reasonable; timeoutSeconds of 2 is short but typical; periodSeconds of 10 is normal.

3. Final Answer:

   The probe path /ready is incorrect or not handled by the app -> Option A

4. Quick Check:

   Probe path must match app endpoint [OK]

Hint: Check if probe path matches app endpoint exactly [OK]

Common Mistakes:

• Ignoring probe path correctness
• Changing timing values unnecessarily
• Assuming timeoutSeconds causes readiness failure

5. You want to configure a Kubernetes HTTP readiness probe that waits 15 seconds after container start, then checks the path /health every 3 seconds, but fails the pod if no response within 1 second. Which is the correct probe configuration snippet?

hard

A. readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 15
periodSeconds: 3
timeoutSeconds: 1

B. readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 3
periodSeconds: 15
timeoutSeconds: 1

C. readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 15
periodSeconds: 1
timeoutSeconds: 3

D. readinessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 1
periodSeconds: 15
timeoutSeconds: 3

Solution

1. Step 1: Match initialDelaySeconds to 15 seconds

   The probe must wait 15 seconds before first check, so initialDelaySeconds: 15.

2. Step 2: Set periodSeconds to 3 seconds and timeoutSeconds to 1 second

   Checks happen every 3 seconds, and timeout is 1 second as required.

3. Final Answer:

   Correct probe with initialDelaySeconds 15, periodSeconds 3, timeoutSeconds 1 -> Option A

4. Quick Check:

   initialDelay=15, period=3, timeout=1 matches requirements [OK]

Hint: Match timing values exactly to requirements [OK]

Common Mistakes:

• Swapping initialDelaySeconds and periodSeconds
• Setting timeoutSeconds longer than periodSeconds
• Using wrong path or port