Pod readiness/liveness HTTP probes timeout when application does not respond quickly enough. Probes fail to reach the health check endpoint within the timeout window.
Kubernetes uses HTTP probes (readiness and liveness) to determine pod health. When application HTTP endpoints do not respond within the probe timeout, the health check fails. This causes Kubernetes to consider the pod unhealthy and may restart or remove it from service.
First diagnostic step
Second diagnostic step
Third diagnostic step
Fourth diagnostic step
Additional notes and platform-specific considerations.
Failed to connect to server: connection refused (HTTP/2)
How to fix "HTTP/2 connection refused" error in Kubernetes
missing request for cpu in container
How to fix "missing request for cpu in container" in Kubernetes HPA
error: invalid configuration
How to fix "error: invalid configuration" in Kubernetes
Fifth diagnostic step