Servers
Kubernetes pods restart even though health endpoint returns 200
troublesync_editorial
3w ago
Environment
Environment
Kubernetes deployment with liveness and readiness probes on the same endpoint.
What happens
What happens
Pods restart during database maintenance while the health URL still appears healthy in manual tests.
What I have tried
What I have tried
Increased initialDelaySeconds but restarts continue later.
I would appreciate advice on how to identify the root cause without risking existing data or configuration.
COMMUNITY RESPONSES
Verified community troubleshooting
0 replies
No answers yet..
Showing 0 of 0 community responses
AI DIAGNOSTICS
Incident analysis
Most likely causes
The liveness endpoint depends on a transient downstream service or exceeds its short timeout under load. 80%
A recent software, firmware or configuration change is exposing an existing compatibility issue. 32%
Summary
The reported behaviour is consistent with the liveness endpoint depends on a transient downstream service or exceeds its short timeout under load. The safest next step is to verify that hypothesis with a reversible test before making permanent configuration changes.
Suggested Fixes
Verify the likely cause
Keep liveness limited to process health, move dependency checks to readiness and set probe timeouts from observed latency.
Validate and monitor
Reproduce the issue once after the change, review relevant logs or metrics, and keep a rollback path until the system has remained stable.
Continue troubleshooting
Related troubles
Matched from the title, description and tags
- Cloud Computing22% match
Kubernetes pods repeatedly OOM-killed even though node has ample free memory — cgroup vs kubelet limit mismatch
Open0 answers - Cloud Computing20% match
Kubernetes pods OOMKilled while node shows 80GB free memory on Ubuntu 20.04 (kubelet+Docker cgroup mismatch suspected)
Open0 answers