From memory
This means your container is running, but the liveness probe detected it's unhealthy (returning HTTP 500). Kubernetes will restart the pod.
Common causes:
- Application crashed or is in a bad state
- Dependency unavailable (database, cache, etc.)
- Resource exhaustion (memory, CPU)
- Configuration error
Troubleshooting:
- Check pod logs:
kubectl logs <pod-name> - Check previous logs if pod restarted:
kubectl logs <pod-name> --previous - Describe the pod for events:
kubectl describe pod <pod-name> - Test the endpoint manually if possible
- Check if the liveness probe is too aggressive (low
initialDelaySeconds or periodSeconds)
Quick fixes:
- Increase
initialDelaySeconds to give the app time to start - Check application health endpoint is actually returning 200
- Verify dependencies are accessible from the pod
No sources. Recorded 2026-10-14.
After looking it up
Based on the passages, an HTTP liveness probe failure with status code 500 indicates that the kubelet received a failure response from the container's health check endpoint.
According to the HTTP probe specification, any status code greater than or equal to 200 and less than 400 indicates success. Any other code indicates failure. A 500 status code falls outside the success range, so the kubelet will consider the container unhealthy.
When a liveness probe fails, the kubelet's response is to kill the container and restart it. This is the expected behavior of a liveness probe—it determines whether a container should be restarted based on whether it is still running and healthy.
The example in the passages demonstrates this: a test server returns a 200 status for the first 10 seconds after the container starts, then returns a 500 status after that. The kubelet, which begins health checks 3 seconds after container startup, will eventually receive the 500 response and restart the container.
If you're seeing this failure unexpectedly, you should verify that your application's health check endpoint is functioning correctly and returning appropriate status codes during normal operation.
Sources
- probes.md — Define a liveness HTTP request
Sources: probes.md — Define a liveness HTTP request; pod-probes-concept.md — Types of probe; probes.md — Define a gRPC liveness probe. Recorded 2026-10-13.