Troubleshooting Guide: Resolving Readiness Probe Failure - HTTP Probe Status Code 503

This guide will help you troubleshoot and resolve issues related to readiness probe failures in your Kubernetes cluster, specifically when encountering the HTTP probe status code 503. Readiness probes are essential for determining when your application is up and running, and Kubernetes should start routing traffic to it.

Table of Contents

  1. Understanding Readiness Probes
  2. Common Causes for Readiness Probe Failure
  3. Step-by-Step Solution
  4. FAQs
  5. Related Links

Understanding Readiness Probes

Readiness probes are used to determine if a container is ready to receive traffic. A pod is considered ready when all of its containers are ready. You can specify the readiness probe in your deployment configuration using the readinessProbe field. Kubernetes uses the readiness probe to check the health of your application periodically.

Readiness probes can be of three types:

  1. HTTP probes: Checks if the application is responding to HTTP requests.
  2. TCP probes: Checks if the container is accepting TCP connections.
  3. Exec probes: Executes a command inside the container and checks the exit status.

Common Causes for Readiness Probe Failure

There are several reasons why your readiness probe might be failing with an HTTP 503 status code:

  1. The application is not running or taking longer than expected to start.
  2. The application is running but not listening on the specified port or path.
  3. The probe configuration is incorrect, causing the probe to fail.

Step-by-Step Solution

Follow these steps to troubleshoot and resolve readiness probe failures with the HTTP status code 503.

Step 1: Check the application logs

Inspect the logs of the affected container using kubectl logs <pod_name> -c <container_name> to identify any issues with the application startup or configuration.

Step 2: Verify the application is running and listening

Ensure that the application is running and listening on the correct port and path. You can use kubectl exec to access the container and check the listening ports using tools like netstat or lsof.

Step 3: Review the readiness probe configuration

Check the readinessProbe configuration in your deployment YAML file. Ensure that the httpGet, port, and path fields are correctly set. For example:

    path: /health
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10

Step 4: Adjust the probe's initial delay and timeout settings

If the application is taking longer to start, you can increase the initialDelaySeconds and timeoutSeconds in the readiness probe configuration. This will give the application more time to start before Kubernetes marks it as not ready.

Step 5: Check the application's health endpoint

If your application exposes a health endpoint, try accessing it directly using curl or a web browser to see if it's returning a 503 status code. If so, you may need to fix your application's health check logic.

Step 6: Apply the changes and verify

After making the necessary changes, apply the updated deployment configuration using kubectl apply -f <deployment_file.yaml>. Verify if the readiness probe is now successful using kubectl describe pod <pod_name>.


1. What is the difference between liveness and readiness probes?

Liveness probes check if the container is running, and if not, Kubernetes will restart the container. Readiness probes, on the other hand, check if the container is ready to receive traffic. Kubernetes will not route traffic to a pod until all of its containers are considered ready.

2. How often does Kubernetes check the readiness probe?

Kubernetes checks the readiness probe at an interval specified by the periodSeconds field in the probe configuration. The default value is 10 seconds.

3. Can I use the same configuration for both liveness and readiness probes?

Yes, you can use the same configuration for liveness and readiness probes if it makes sense for your application. However, it's essential to understand the differences between the two probes and ensure that using the same configuration doesn't lead to unintended consequences.

4. Can I have multiple readiness probes for a single container?

No, you can only have one readiness probe per container. If you need to check multiple conditions, you can implement a custom health check script that checks all required conditions and use an exec probe to run the script.

5. How do I disable the readiness probe for a container?

To disable the readiness probe for a container, remove the readinessProbe field from the container's configuration in the deployment YAML file.

  1. Kubernetes Documentation: Configure Liveness, Readiness, and Startup Probes
  2. Kubernetes Documentation: Pod Lifecycle
  3. Kubernetes Documentation: Container probes

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.