A developer deploys a pod that continuously restarts. 'kubectl describe pod' shows the container exits with code 137. What is the most likely cause?
Trap 1: The liveness probe is failing and restarting the container.
Liveness probe failure restarts the container but exit code is not typically 137.
Trap 2: The init container is failing and blocking the main container.
Init container failure would prevent the main container from starting at all.
Trap 3: The pod is hitting a resource quota limit at the namespace level.
Resource quota prevents creation, not runtime OOM.
- A
The container is exceeding its memory limit and being OOM-killed.
Exit code 137 indicates SIGKILL, often from OOM.
- B
The liveness probe is failing and restarting the container.
Why wrong: Liveness probe failure restarts the container but exit code is not typically 137.
- C
The init container is failing and blocking the main container.
Why wrong: Init container failure would prevent the main container from starting at all.
- D
The pod is hitting a resource quota limit at the namespace level.
Why wrong: Resource quota prevents creation, not runtime OOM.