Question

A pod in your GKE Standard cluster keeps restarting with a CrashLoopBackOff status. You need to quickly inspect the application's stdout/stderr output from the most recent failed container run to diagnose the issue. Which command should you use?

Accepted Answer

kubectl logs <pod-name> --previous

Answer

kubectl describe pod <pod-name>

Answer

kubectl get events --field-selector involvedObject.name=<pod-name>

Answer

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