[Verse 1]
When your pod is running but something's going wrong
You need to peek inside to see what's going on
Kubectl logs with your pod name in tow
Will show you all the messages your container needs you to know
[Chorus]
Get pod logs, see what's there
Kubectl logs shows you what's happening where
Dash f to follow, dash dash tail for the end
Previous crashed instance, logs are your friend
Get pod logs, make it clear
Debug your pods when errors appear
[Verse 2]
Multi-container pods need a little more care
Add dash c with container name to get exactly where
The messages are coming from, which service is the source
When multiple containers run, you'll need to stay on course
[Chorus]
Get pod logs, see what's there
Kubectl logs shows you what's happening where
Dash f to follow, dash dash tail for the end
Previous crashed instance, logs are your friend
Get pod logs, make it clear
Debug your pods when errors appear
[Bridge]
Dash dash previous when your pod has crashed
Shows the logs from before when everything was smashed
Dash dash tail one hundred gives you just the last
Skip the older messages, get current info fast
[Verse 3]
Stream the logs in real time with dash f flag
Watch them scroll before your eyes, no need to lag
Following live output as your application runs
Debugging gets much easier when live logging's begun
[Chorus]
Get pod logs, see what's there
Kubectl logs shows you what's happening where
Dash f to follow, dash dash tail for the end
Previous crashed instance, logs are your friend
Get pod logs, make it clear
Debug your pods when errors appear
[Outro]
Pod name first, then your flags
Container name when needed, no more debug snags
Kubectl logs will guide your way
To healthier pods every day