Practice the basic troubleshooting flow for a pod using get, describe, logs, and exec.
Build a simple debugging sequence you can use during Kubernetes incidents and interviews.
Check the current pod state in the namespace.
Command
kubectl get podsExpected Result
You should see the pod names and current statuses.
Inspect events, scheduling issues, restart counts, and probe failures.
Command
kubectl describe pod <pod-name>Expected Result
You should see detailed pod information and recent events.
Review application logs to identify startup or runtime problems.
Command
kubectl logs <pod-name>Expected Result
You should see the container logs and any visible application errors.
Inspect environment variables, config files, or service connectivity from inside the running container.
Command
kubectl exec -it <pod-name> -- shExpected Result
You should get an interactive shell inside the pod.
Confirm whether the Deployment rollout completed or is still failing.
Command
kubectl rollout status deployment/<deployment-name>Expected Result
You should see rollout success or rollout failure details.
You can follow a clean Kubernetes troubleshooting flow.
You know when to use get, describe, logs, exec, and rollout status.