[Verse 1] When your deployment's running wild And changes aren't going as planned You need to see what happened when Each rollout took command There's a simple way to trace Every version that's been deployed Just use kubectl with the right grace And your history won't be destroyed [Chorus] Rollout history, rollout history Shows you every change that's been made Kubectl rollout history deployment name That's the command that won't fade From revision one to the latest run You can see them all in line Rollout history, rollout history Makes debugging shine [Verse 2] Type kubectl rollout history first Then deployment slash your name Watch the revisions appear in order Like a timeline of your game Each number tells a story Of when changes were applied From the first deployment glory To the current running pride [Chorus] Rollout history, rollout history Shows you every change that's been made Kubectl rollout history deployment name That's the command that won't fade From revision one to the latest run You can see them all in line Rollout history, rollout history Makes debugging shine [Bridge] But wait there's more to see When you need specific details Add revision equals two And watch as knowledge never fails The dash dash revision flag Will show you what you need Deep dive into any change At debugging speed [Verse 3] Sometimes you need the full story Of one particular deploy Add dash dash revision number And details you'll enjoy See exactly what was changed In that specific run Compare it to the others Till your debugging's done [Chorus] Rollout history, rollout history Shows you every change that's been made Kubectl rollout history deployment name That's the command that won't fade From revision one to the latest run You can see them all in line Rollout history, rollout history Makes debugging shine [Outro] So when your pods aren't working right And you need to trace the past Rollout history is your friend It'll help you find answers fast
← Jobs (run-to-completion tasks) | Expose a deployment as a service →