Production environment on Amazon EKS. The pod was working fine until a deployment 30 minutes ago.
The interviewer asks“A critical microservice pod keeps restarting with CrashLoopBackOff status. The on-call engineer has escalated to you. How do you diagnose and resolve this?”
Check pod events with kubectl describe, get container logs from the failing and previous container, inspect exit codes, verify liveness/readiness probes, check resource limits, and inspect recent deployment changes.
A free account unlocks the rest of it, and saves your progress across every track.
kubectl get List Kubernetes resources and their statuskubectl describe Explain an object's state, conditions and eventskubectl logs Read and follow container logskubectl exec Run a command or shell inside a running containerkubectl apply Create or update resources from YAML, declarativelykubectl delete Delete Kubernetes resources safelykubectl scale Change the replica count of a workloadkubectl rollout Watch, undo and restart Deployment rollouts