[Verse 1] When your pod is running strong and free But you need to peek inside and see There's a command that opens up the door kubectl exec will give you so much more Type dash i and dash t together tight Interactive terminal shining bright Then the pod name that you want to reach Shell access is within your teach [Chorus] Execute into the running pod Dash i dash t, remember the code Kubectl exec will take you there Inside the container, commands to share Execute into the running pod Double dash bin slash sh, break the facade When you need to troubleshoot and debug Step inside with the terminal hug [Verse 2] Sometimes you've got multiple containers inside Need to specify which one to ride Add dash c and then the container name Before the double dash, play the game Bin slash bash if you want more power Advanced shell for that coding hour But bin slash sh works most of the time Simple shell that works just fine [Chorus] Execute into the running pod Dash i dash t, remember the code Kubectl exec will take you there Inside the container, commands to share Execute into the running pod Double dash bin slash sh, break the facade When you need to troubleshoot and debug Step inside with the terminal hug [Bridge] Interactive mode with dash i flag Terminal session, never lag Dash t gives you that TTY Pretty output for your eye When things go wrong and logs aren't clear Jump inside, the truth appears File systems, processes running wild Debugging made simple, error reconciled [Chorus] Execute into the running pod Dash i dash t, remember the code Kubectl exec will take you there Inside the container, commands to share Execute into the running pod Double dash separates, don't be awed When you need to troubleshoot and debug Step inside with the terminal hug [Outro] From the outside looking in To the inside where you win Execute and investigate Kubectl exec is truly great
← Get pod logs | Describe a pod (events, conditions, container status) →