Why Liveness and readiness probes in Microservices? - Purpose & Use Cases

The Big Idea

What if your app could fix itself before users even notice a problem?

The Scenario

Imagine you run a busy restaurant kitchen where chefs sometimes get tired or stuck. Without anyone checking, orders pile up, and customers wait forever. You have no way to know if a chef is ready to cook or needs a break.

The Problem

Manually checking each chef's status is slow and error-prone. You might miss when a chef is stuck or not ready, causing delays and unhappy customers. It's like guessing if a service is healthy without clear signals.

The Solution

Liveness and readiness probes act like kitchen managers who constantly check if chefs are alive and ready to cook. They automatically detect problems and help restart or pause services, keeping everything running smoothly without guesswork.

Before vs After

✗ Before

if service_responds():
    process_request()
else:
    guess_restart_service()

✓ After

readiness_probe = check_service_ready()
liveness_probe = check_service_alive()
if readiness_probe and liveness_probe:
    process_request()
else:
    restart_or_wait()

What It Enables

It enables automatic, reliable health checks that keep microservices running smoothly and users happy without manual intervention.

Real Life Example

In a ride-sharing app, readiness probes ensure the driver service only accepts rides when fully ready, while liveness probes restart it if it crashes, preventing lost rides and frustrated users.

Key Takeaways

Manual health checks are slow and unreliable.

Liveness and readiness probes automate service health monitoring.

This leads to more stable, responsive microservices.

Practice

1. What is the main purpose of a liveness probe in microservices?

easy

A. To check if the service is ready to accept traffic

B. To log user requests for debugging

C. To monitor the network latency between services

D. To check if the service is alive and restart it if it is not

Solution

1. Step 1: Understand the role of liveness probes

   Liveness probes detect if a service is stuck or dead and need restarting.

2. Step 2: Differentiate from readiness probes

   Readiness probes check if the service can handle requests, not if it is alive.

3. Final Answer:

   To check if the service is alive and restart it if it is not -> Option D

4. Quick Check:

   Liveness probe = check alive and restart [OK]

Hint: Liveness = alive and restart, Readiness = ready for traffic [OK]

Common Mistakes:

• Confusing liveness with readiness probes
• Thinking liveness probes check traffic readiness
• Assuming liveness probes monitor performance

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

easy

A. livenessProbe:
exec:
command: ["cat", "/tmp/healthy"]
timeoutSeconds: 1

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

C. readinessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 5
periodSeconds: 10

D. livenessProbe:
httpGet:
path: /ready
port: 8080
failureThreshold: 3

Solution

1. Step 1: Identify readiness probe syntax

   Readiness probes often use httpGet with path and port, plus delay and period settings.

2. Step 2: Confirm correct fields and indentation

   readinessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 periodSeconds: 10 correctly shows readinessProbe with httpGet, initialDelaySeconds, and periodSeconds.

3. Final Answer:

   readinessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 periodSeconds: 10 -> Option C

4. Quick Check:

   Readiness probe syntax = readinessProbe: httpGet: path: /healthz port: 8080 initialDelaySeconds: 5 periodSeconds: 10 [OK]

Hint: Readiness uses httpGet with path and port in YAML [OK]

Common Mistakes:

• Mixing livenessProbe and readinessProbe fields
• Incorrect indentation in YAML
• Using wrong probe type for readiness

3. Given this Kubernetes pod spec snippet, what will happen if the readiness probe fails continuously?

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

medium

A. The pod will be restarted immediately

B. The pod will be marked as not ready and removed from service endpoints

C. The pod will ignore the failure and continue serving traffic

D. The pod will scale up automatically

Solution

1. Step 1: Understand readiness probe failure effect

   Readiness probe failure marks pod as not ready, so it stops receiving traffic.

2. Step 2: Differentiate from liveness probe effect

   Liveness probe failure triggers pod restart, readiness does not.

3. Final Answer:

   The pod will be marked as not ready and removed from service endpoints -> Option B

4. Quick Check:

   Readiness failure = pod not ready, no restart [OK]

Hint: Readiness failure removes pod from load balancer, no restart [OK]

Common Mistakes:

• Confusing readiness failure with pod restart
• Assuming pod scales automatically on probe failure
• Ignoring failureThreshold effect

4. A microservice has a liveness probe configured as an HTTP GET on /health. The service sometimes returns HTTP 500 during startup but is healthy afterward. What is the best fix to avoid unnecessary restarts?

medium

A. Increase initialDelaySeconds to allow startup time before probing

B. Change the probe to readiness probe instead of liveness probe

C. Remove the probe completely to avoid restarts

D. Set failureThreshold to 1 to detect failures faster

Solution

1. Step 1: Identify cause of restarts

   Liveness probe fails during startup because service returns HTTP 500 before ready.

2. Step 2: Adjust probe timing to avoid false failures

   Increasing initialDelaySeconds delays probe start, allowing service to become healthy first.

3. Final Answer:

   Increase initialDelaySeconds to allow startup time before probing -> Option A

4. Quick Check:

   Delay liveness probe start to avoid false failures [OK]

Hint: Delay liveness probe start to avoid false failure during startup [OK]

Common Mistakes:

• Removing probes which reduces reliability
• Confusing readiness and liveness probe roles
• Setting failureThreshold too low causing quick restarts

5. You have a microservice that takes time to initialize resources before it can serve requests. You want to ensure it is not restarted unnecessarily but also not receive traffic before ready. How should you configure liveness and readiness probes?

hard

A. Set liveness probe with a longer initialDelaySeconds and readiness probe to check resource initialization

B. Use only a liveness probe with a short periodSeconds to restart fast

C. Use only a readiness probe and no liveness probe

D. Set both probes to the same HTTP path and timing

Solution

1. Step 1: Prevent unnecessary restarts during initialization

   Set liveness probe initialDelaySeconds long enough to avoid restarting while initializing.

2. Step 2: Use readiness probe to block traffic until ready

   Readiness probe should check if resources are initialized before accepting traffic.

3. Final Answer:

   Set liveness probe with a longer initialDelaySeconds and readiness probe to check resource initialization -> Option A

4. Quick Check:

   Liveness delay + readiness check = safe startup [OK]

Hint: Delay liveness, readiness blocks traffic until ready [OK]

Common Mistakes:

• Using only one probe type causing traffic or restart issues
• Setting same path and timing for both probes
• Not delaying liveness probe causing premature restarts