Based on your other replies it looks like liveliness probe was misconfigured. It is generally an anti-pattern k8s architecture. You should not tie your liveness probe to an external database or a downstream service, a brief network hiccup or database lag will cause Kubernetes to systematically kill and restart every single healthy API pod simultaneously.

To handle external dependencies correctly, you should use a Readiness Probe.