1
Verify the likely cause
Keep liveness limited to process health, move dependency checks to readiness and set probe timeouts from observed latency.
FULL AI ANALYSIS
Kubernetes pods restart even though health endpoint returns 200
Generated Sep 22, 2026, 11:55:04 PM
Analysis 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.
Possible 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%Suggested fixes
2
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.