After running kubectl debug pod/api-1 -c debug --image=busybox, you cannot see the debug container in kubectl get pods. Why?

medium📝 Troubleshoot Q7 of 15

Kubernetes - Troubleshooting

After running kubectl debug pod/api-1 -c debug --image=busybox, you cannot see the debug container in kubectl get pods. Why?

Akubectl get pods only shows pods, not containers

BThe debug container failed to start and was removed

CDebug containers run as ephemeral containers and do not appear as separate pods

DYou need to add --show-containers flag to see debug containers

Step-by-Step Solution

Solution:

Step 1: Understand ephemeral containers
Debug containers created by kubectl debug run as ephemeral containers inside existing pods, not as separate pods.
Step 2: Check kubectl get pods output
kubectl get pods lists pods, not individual containers inside pods, so debug containers do not appear separately.
Final Answer:
Debug containers run as ephemeral containers and do not appear as separate pods -> Option C
Quick Check:
Ephemeral containers are inside pods, not separate pods [OK]

Quick Trick: Ephemeral debug containers don't show as separate pods [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