After deploying a new tax-forms API image, Pods enter CrashLoopBackOff. What systematic first path best identifies why the container exits?
Select an answer to reveal the explanation.
Short Explanation
CrashLoopBackOff is the cluster saying the app keeps falling over on boot. Describe for the exit clue, logs for the last words, then fix the image, command, or config. Scaling to zero just hides the patient.
Full Explanation
CrashLoopBackOff indicates the container starts, exits non-zero, and is restarted until backoff delays grow. Effective debugging inspects Pod events and container state via kubectl describe, reads current and previous logs, then corrects the application image, entrypoint/args, or configuration. Scaling away the workload, blocking egress, or tweaking unrelated token audiences does not explain or fix the crash cause.