kubectl Narration
5 exercises — Practice describing kubectl output, pod states, and diagnostic sequences in professional English.
0 / 5 completed
Quick reference: kubectl output vocabulary
- READY column — format is <passing>/<total> containers; reflects readiness probe results
- CrashLoopBackOff — container exits non-zero; Kubernetes restarts with exponential backoff delay
- --previous flag — retrieves logs from the last terminated (crashed) container instance
1 / 5
Your team is triaging a deployment issue. In kubectl get pods output, a pod shows READY: 0/1 and STATUS: Running. A junior engineer asks what "0/1" means. Which response most accurately explains the READY column?
The READY column shows how many containers in the pod have passed their readiness probe — "0/1" means none of the pod's one container is ready to serve traffic.
A pod can be in STATUS Running (the container process has started) while still showing READY 0/1 if its readiness probe has not yet returned a successful response. Until the readiness probe passes, Kubernetes removes the pod from the Service's Endpoints, so no traffic is routed to it. This distinction is important when explaining why a deployment looks healthy but requests are failing.
Key vocabulary:
• READY column — format is <passing containers>/<total containers>; reflects readiness probe results
• readiness probe — a periodic check that determines whether a pod should receive traffic
• Endpoints — the list of pod IPs a Service forwards traffic to; pods excluded when not ready
A pod can be in STATUS Running (the container process has started) while still showing READY 0/1 if its readiness probe has not yet returned a successful response. Until the readiness probe passes, Kubernetes removes the pod from the Service's Endpoints, so no traffic is routed to it. This distinction is important when explaining why a deployment looks healthy but requests are failing.
Key vocabulary:
• READY column — format is <passing containers>/<total containers>; reflects readiness probe results
• readiness probe — a periodic check that determines whether a pod should receive traffic
• Endpoints — the list of pod IPs a Service forwards traffic to; pods excluded when not ready