Kubernetes - Service Mesh
After injecting Linkerd proxy into a pod, what is the expected change in pod status when running
kubectl get pods?After injecting Linkerd proxy into a pod, what is the expected change in pod status when running kubectl get pods?
medium📝 Command Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand proxy injection effect
Linkerd adds a sidecar proxy container to the pod without stopping it.Step 2: Check pod status after injection
The pod remains 'Running' with an extra container visible.Final Answer:
Pod status remains 'Running' with additional sidecar container -> Option BQuick Check:
Sidecar injection keeps pod running = A [OK]
Quick Trick: Injected pods run with extra proxy container [OK]
Common Mistakes:
- Expecting pod to restart or crash
- Thinking pod status changes to Pending
- Assuming pod deletion after injection
Master "Service Mesh" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes