Readiness probe concept in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of a Readiness Probe in Kubernetes

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

A To check if the container is alive and restart it if it is not

B To determine if the container is ready to accept traffic

C To monitor resource usage like CPU and memory inside the container

D To automatically scale the number of pods based on load

💡 Hint

Think about when Kubernetes should send traffic to a pod.

A readiness probe tells Kubernetes if a pod is ready to receive requests. If the probe fails, the pod is removed from service endpoints until it passes again.

💻 Command Output

intermediate

Readiness Probe Failure Effect

Given a pod with a readiness probe that fails continuously, what will be the state of the pod in the Kubernetes service endpoints?

A The pod will be removed from the service endpoints and not receive traffic

B The pod will be restarted automatically by Kubernetes

C The pod will be deleted from the cluster

D The pod will remain in the service endpoints and receive traffic

💡 Hint

Consider what happens when a pod is not ready but still running.

If the readiness probe fails, Kubernetes stops sending traffic to the pod by removing it from service endpoints, but it does not restart or delete the pod.

❓ Configuration

advanced

Correct Readiness Probe Configuration

Which of the following YAML snippets correctly configures a readiness probe that checks HTTP path /health on port 8080 every 10 seconds with a timeout of 5 seconds?

A

readinessProbe:
  httpGet:
    path: /health
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10
  timeoutSeconds: 5

B

readinessProbe:
  httpGet:
    path: /health
    port: 8080
  periodSeconds: 5
  timeoutSeconds: 10

C

readinessProbe:
  exec:
    command: ["curl", "-f", "http://localhost:8080/health"]
  periodSeconds: 10
  timeoutSeconds: 5

D

readinessProbe:
  tcpSocket:
    port: 8080
  periodSeconds: 10
  timeoutSeconds: 5

💡 Hint

Look for the HTTP GET method with correct timing settings.

Option A correctly uses httpGet with the right path, port, and timing parameters. Other options either use wrong timing or different probe types.

❓ Troubleshoot

advanced

Troubleshooting Readiness Probe Failures

A pod's readiness probe is failing, but the container is running fine. Which of the following is the most likely cause?

A The pod has insufficient CPU resources

B The container is crashing and restarting frequently

C The readiness probe path or port is incorrect or the service inside the container is not responding

D The pod's liveness probe is misconfigured

💡 Hint

Think about what the readiness probe checks specifically.

Readiness probes check if the container is ready to serve traffic, often by hitting a specific path or port. If that path or port is wrong or the service is not responding, the probe fails even if the container is running.

🔀 Workflow

expert

Readiness Probe Impact on Rolling Updates

During a rolling update, how does a failing readiness probe affect the deployment rollout process?

A Kubernetes immediately rolls back the update if any pod fails its readiness probe

B Pods failing readiness probes are restarted repeatedly until they pass, blocking rollout progress

C Kubernetes pauses the rollout indefinitely until all pods pass readiness probes

D Pods failing readiness probes are not added to the service endpoints, so traffic is not sent to them, but rollout continues until maxUnavailable is reached

💡 Hint

Consider how Kubernetes balances availability and rollout progress.

Kubernetes removes pods failing readiness probes from service endpoints so they don't receive traffic. The rollout continues respecting maxUnavailable limits, allowing some pods to be unavailable temporarily.