Kubectl Debugging Deck
Recall the first diagnostic command for common Kubernetes workload symptoms.
mixed-card-deck score-chips comparison Events A Pod is Pending. What evidence should you read first? Think scheduling and kubelet events. kubectl describe pod Events can show unsatisfied resources, node selectors, taints, image pull issues, and mount problems. Restarts A Pod is in CrashLoopBackOff. Which logs are easy to forget? The current container may not contain the last failure. kubectl logs --previous Previous logs preserve what the crashed container emitted before Kubernetes restarted it. Rollout Status vs. history: what do they answer during a bad Deployment? Use both when user symptoms start immediately after a release. Objection Let's exec into a Pod…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in