Question

A deployment's pods are stuck and never become Ready. Running 'kubectl get pods' shows STATUS 'Init:CrashLoopBackOff' for every pod. The application container itself has not started yet. You need to identify the root cause. Which command gives you the most direct diagnostic information about why the pods cannot start?

Accepted Answer

kubectl logs -c

Answer

kubectl logs <pod>

Answer

kubectl top pod <pod>

Answer

kubectl exec <pod> -- cat /var/log/app.log