medium10 pts · first answer countsdeploymentreliability

Errors during every deploy

During each rolling deploy on Kubernetes, clients see a burst of 502 errors as old pods stop. What should the app do when it receives SIGTERM?

A.Call process.exit(0) right away, since Kubernetes already moved all traffic to the new pod before sending the signalB.Ignore SIGTERM so the pod is never stoppedC.Stop taking new connections, finish in-flight requests, close the DB pool, then exitD.Restart itself in the same container

← Webhook signature never matches Liveness probe restarts every pod →