[Verse 1]
When your pods need private images from a registry far away
You can't just pull them down without the proper auth today
Docker secrets hold the keys to unlock that private door
Let me show you how to make one, then your pods can pull much more
[Chorus]
Kubectl create secret docker-registry name
Docker server, username, password - remember this refrain
Four parameters you need to make the magic work just right
Registry secrets unlock the images hidden from plain sight
[Verse 2]
Start with kubectl create secret, then docker-registry type
Give it any name you want, just make sure that name is right
Docker server takes the URL where your private images stay
Like registry dot example dot com pointing the way
[Chorus]
Kubectl create secret docker-registry name
Docker server, username, password - remember this refrain
Four parameters you need to make the magic work just right
Registry secrets unlock the images hidden from plain sight
[Bridge]
Docker username holds the account that has the proper access
Docker password is the key that makes the login process
Once you've run this simple command your secret will be stored
Ready for your pods to use when images need to be explored
[Verse 3]
Now your Kubernetes cluster holds the credentials safe and sound
When pods need those private images, authentication will be found
Reference this secret in your specs and watch the magic flow
Private registries open up and let your containers go
[Chorus]
Kubectl create secret docker-registry name
Docker server, username, password - remember this refrain
Four parameters you need to make the magic work just right
Registry secrets unlock the images hidden from plain sight
[Outro]
Server, username, password, name
Docker registry secrets tame
Four flags to remember well
Private images you can tell