[Verse 1] When your pod is acting strange and you don't know why There's a command that shows the truth, no need to cry Kubectl describe pod, just type the name It tells the story of what's happening in the game [Chorus] Describe describe, show me what's inside Events and conditions, container's ride Status and phases, all laid out clear Kubectl describe pod makes problems disappear [Verse 2] First it shows the metadata, name and namespace too Labels and annotations, all the tags on you Then the spec section tells us what should be The image and the ports and resources we need [Chorus] Describe describe, show me what's inside Events and conditions, container's ride Status and phases, all laid out clear Kubectl describe pod makes problems disappear [Verse 3] Container status tells us if it's running fine Ready, waiting, terminated - check the line Restart count and reason why it failed before Image pull status tells us so much more [Bridge] Events at the bottom, chronological flow Shows you the journey, how your pod did grow Scheduled and pulling, started and crashed All the important moments, nothing gets trashed [Chorus] Describe describe, show me what's inside Events and conditions, container's ride Status and phases, all laid out clear Kubectl describe pod makes problems disappear [Outro] So when debugging gets you down Describe your pod and turn it around The answer's there in black and white Kubectl describe makes everything right
← Execute into a running pod | Port-forward to a pod (local debugging) →