What happens if you run kubectl debug pod/web-2 --image=busybox -- sh but the pod web-2 is in CrashLoopBackOff state?

medium📝 Command Output Q5 of 15

Kubernetes - Troubleshooting

What happens if you run kubectl debug pod/web-2 --image=busybox -- sh but the pod web-2 is in CrashLoopBackOff state?

AThe pod is automatically restarted

BDebug container starts successfully in the pod's namespace

Ckubectl debug fails because the pod is not running

Dkubectl debug deletes the pod

Step-by-Step Solution

Solution:

Step 1: Understand pod state impact
If the pod is in CrashLoopBackOff, it is not in a stable running state, so kubectl debug cannot attach a debug container.
Step 2: Check command behavior
The debug command fails because it requires the pod to be running to create a debug container in its namespace.
Final Answer:
kubectl debug fails because the pod is not running -> Option C
Quick Check:
Pod must be running for kubectl debug to succeed [OK]

Quick Trick: Pod must be running; CrashLoopBackOff blocks debug container [OK]

Common Mistakes:

Master "Troubleshooting" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes