medium10 pts · first answer countsdeploymentreliabilityobservability

Liveness probe restarts every pod

Your liveness probe checks the database. During a two-minute database outage, Kubernetes keeps restarting every API pod, making recovery slower. What is the better design?

A.Liveness checks only that the process responds; readiness says whether the pod can serve traffic nowB.Remove all probes from the deploymentC.Keep the database check in liveness but raise failureThreshold so pods restart only after a few minutes of failuresD.Make the readiness probe always return 200

← Errors during every deploy Retrying after a shared outage →