Kubernetes - Troubleshooting
What will be the output when running
kubectl debug pod/web-1 --image=busybox -- sh if the pod web-1 exists and is running?What will be the output when running kubectl debug pod/web-1 --image=busybox -- sh if the pod web-1 exists and is running?
medium📝 Command Output Q4 of 15
Step-by-Step Solution
Solution:
Step 1: Understand command behavior
This command creates a new debug container using the busybox image and opens a shell (sh) inside the pod's namespace.Step 2: Check pod existence
Since podweb-1exists and is running, the debug container starts successfully.Final Answer:
Starts a new debug container with a shell inside the pod namespace -> Option BQuick Check:
Running kubectl debug on existing pod = new debug container [OK]
Quick Trick: kubectl debug runs new container in pod's namespace [OK]
Common Mistakes:
- Expecting pod deletion
- Confusing debug with scaling
- Assuming error if pod exists
Master "Troubleshooting" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes