Question

A developer creates a bare Pod (not managed by a Deployment) that runs a container executing a one-time data migration script. They set the Pod's restartPolicy to its default value. After the script finishes successfully and the container exits with code 0, they notice the container keeps starting again. Which explanation correctly describes why this happens?

Accepted Answer

The default restartPolicy for a Pod is Always, so the kubelet restarts the container even after a successful exit.

Answer

The default restartPolicy is OnFailure, and a zero exit code is treated as a failure requiring a restart.

Answer

A Pod's containers are always restarted regardless of restartPolicy because the scheduler re-binds the Pod.

Answer

The default restartPolicy is Never, but the API server automatically overrides it for single-container Pods.