How would you diagnose a Pod that is stuck in CrashLoopBackOff?

• A. Delete the Pod and recreate it.
• B. Restart the cluster.
• C. Ignore; it's expected.
• D. Check logs with oc logs, describe for events, check container exit codes, and inspect recent changes in YAML or image.

Answer: (D)

CrashLoopBackOff means the container inside the pod keeps starting and then exiting, so Kubernetes keeps restarting it. To diagnose, you want to pull the logs from the running container to see what error or exception the application is emitting; if the crash happens too quickly for the current container, also look at the previous instance with the --previous option to view the last terminated container’s logs. Describe the pod to surface events and reasons for restarts—these events can reveal issues like image pull failures, insufficient resources, or health check problems. Check the container’s exit codes from the pod status or describe output to understand how the process terminated. Finally, review recent changes in the pod’s configuration or image: updates to the YAML in the Deployment/StatefulSet, environment variables, resource limits, or the image tag can introduce startup failures. This combination of logs, events, exit codes, and recent changes points you toward the root cause, whether it’s a code error, misconfiguration, or an image problem.