Kubernetes Administration Essentials
19 chapters
1. View network policies
[Verse 1]
When you need to see the rules that guard your cluster's flow
Network policies control the traffic, high and low
Use kubectl get to view them all across the space
Add dash A flag to see them in every namespace
[Chorus]
View network policies, see who talks to who
Get network policies, that's what admins do
Dash A shows all namespaces, every single one
Network policies keep your cluster secure and strong
[Verse 2]
From day one implement the best practice way
Default deny all traffic, then whitelist what can stay
Start with zero trust model, block everything at first
Then open up the channels for the traffic that you trust
[Chorus]
View network policies, see who talks to who
Get network policies, that's what admins do
Dash A shows all namespaces, every single one
Network policies keep your cluster secure and strong
[Bridge]
When services need to talk across namespace lines
Use FQDN service names, that's how you define
Service dot namespace dot svc dot cluster dot local
That's the proper format for communication protocol
[Verse 3]
Configuration and secrets come next in our song
ConfigMaps hold the settings that help services run strong
But first secure your network with policies in place
View them with kubectl across every namespace
[Chorus]
View network policies, see who talks to who
Get network policies, that's what admins do
Dash A shows all namespaces, every single one
Network policies keep your cluster secure and strong
[Outro]
Default deny, then whitelist
That's the security checklist
View your policies today
Keep the bad traffic away
2. Rollback to previous version
[Verse 1]
When your deployment goes astray
And the new version breaks today
Don't panic when the users call
There's a command to fix it all
Kubectl rollout undo saves the day
Takes you back to yesterday
Just add deployment and the name
Your system's running right again
[Chorus]
Roll it back, roll it back
When the current version's cracked
Undo deployment by name
Makes it work the same
Roll it back, roll it back
Get your system on the track
Kubectl rollout undo
That's what you need to do
[Verse 2]
Sometimes you need a specific place
Not just the previous embrace
Add the flag to revision three
Or whatever number it should be
Version history keeps the trail
Of every update without fail
Choose the number that worked before
That's what revision flags are for
[Chorus]
Roll it back, roll it back
When the current version's cracked
Undo deployment by name
Makes it work the same
Roll it back, roll it back
Get your system on the track
Kubectl rollout undo
That's what you need to do
[Bridge]
To revision equals the number you choose
Three or five or two you can use
Previous version is the default way
When you don't specify the day
Quick recovery from your mistake
Rolling back for your users' sake
[Chorus]
Roll it back, roll it back
When the current version's cracked
Undo deployment by name
Makes it work the same
Roll it back, roll it back
Get your system on the track
Kubectl rollout undo
That's what you need to do
[Outro]
When deployments go wrong today
Remember rollback is the way
3. 5 Troubleshooting Common Issues
[Verse 1]
Pod is crashing, spinning round and round
CrashLoopBackOff brings your cluster down
Check your memory limits, CPU too tight
Storage volumes missing, config not right
Kafka brokers failing, logs will show the way
Resource constraints keeping pods at bay
[Chorus]
Five big problems, learn them well
CRASH and CERT and NETWORK hell
Under-replicated, OPERATOR stuck
REBALANCE storms - you're out of luck
But we'll debug them one by one
Till your Kafka cluster runs
[Verse 2]
Certificates expired, TLS won't connect
Rotation failed, what did you expect?
Check the secret volumes, dates have passed
Trust stores broken, connections don't last
Operator should renew them automatically
But sometimes manual steps set you free
[Chorus]
Five big problems, learn them well
CRASH and CERT and NETWORK hell
Under-replicated, OPERATOR stuck
REBALANCE storms - you're out of luck
But we'll debug them one by one
Till your Kafka cluster runs
[Verse 3]
Network's broken, DNS can't resolve
Firewall blocking, security to solve
Check your service names and namespace calls
Security groups might be building walls
Pods can't reach each other cross the wire
Network policies might block your fire
[Chorus]
Five big problems, learn them well
CRASH and CERT and NETWORK hell
Under-replicated, OPERATOR stuck
REBALANCE storms - you're out of luck
But we'll debug them one by one
Till your Kafka cluster runs
[Verse 4]
Partitions under-replicated, ISR shrinking fast
Brokers can't keep up, performance won't last
Check your replica factor, min-ISR too
Broker health is failing, what will you do?
Replication broken means data at risk
Fix it quickly, don't be brisk
[Verse 5]
Operator stuck, not reconciling state
RBAC permissions seal your fate
CRD versions mismatched, old and new
Cluster operator doesn't know what to do
Check your service accounts, roles and binds
Custom resource definitions in your minds
[Verse 6]
Consumer rebalancing, storms arise
Group coordinator can't synchronize
Too many consumers joining at once
Protocol thrashing, makes you a dunce
Partition assignment takes too long
Rebalance timeout, something's wrong
[Bridge]
From pods to certs to network calls
Under-replication, operator stalls
Consumer chaos, rebalancing pain
But now you know how to fix again
[Chorus]
Five big problems, now you know
CRASH and CERT and NETWORK flow
Under-replicated, OPERATOR clear
REBALANCE storms - nothing to fear
You can debug them one by one
Your Kafka cluster's gonna run
[Outro]
Strimzi mastery in your hands
Troubleshooting helps you understand
Five common issues, solutions bright
Your Kubernetes Kafka's running right
4. List ingress resources
[Verse 1]
When your traffic needs a gateway to the cluster door
Ingress resources are what you're looking for
They route the requests from outside to in
Let's learn to list them, that's where we begin
[Chorus]
kubectl get ingress dash A
Shows them all across the way
Every namespace, every route
Traffic flowing through and through
Get ingress dash A today
Lists them all without delay
[Verse 2]
The dash A flag means all namespaces wide
No single namespace to hide behind
You'll see the hosts and the backend names
The rules that guide the traffic games
[Chorus]
kubectl get ingress dash A
Shows them all across the way
Every namespace, every route
Traffic flowing through and through
Get ingress dash A today
Lists them all without delay
[Bridge]
Name and namespace in the first columns you'll find
Class and hosts showing how they're designed
Address and ports tell you where they bind
Age shows how long they've been assigned
[Verse 3]
From default namespace to kube-system too
Production, staging, development crew
One single command shows the complete view
All ingress resources displayed for you
[Chorus]
kubectl get ingress dash A
Shows them all across the way
Every namespace, every route
Traffic flowing through and through
Get ingress dash A today
Lists them all without delay
[Outro]
So when you need to see the traffic flow
All ingress resources in one show
Remember the A flag, let your knowledge grow
kubectl get ingress dash A, now you know
5. Create from literal values
[Verse 1]
When you need data stored inside your cluster
ConfigMaps are the way to go
From literal values, build your configuration
Let me teach you what you need to know
Start with kubectl, then create configmap
Give it any name you choose
Add from literal flag, then key equals value
That's the pattern you will use
[Chorus]
From literal, from literal
Key equals value every time
From literal, from literal
Each setting on a separate line
Double dash from literal
That's the flag you need to know
Build your config piece by piece
Watch your application grow
[Verse 2]
Maybe you need database connection strings
Or perhaps some feature flags
Each key value pair gets its own from literal
No more complicated tags
First key might be database host
Second could be database port
Chain them together with multiple flags
Clean configuration, nice and short
[Chorus]
From literal, from literal
Key equals value every time
From literal, from literal
Each setting on a separate line
Double dash from literal
That's the flag you need to know
Build your config piece by piece
Watch your application grow
[Bridge]
No files needed, no complex setup
Just type the values as you go
Direct and simple, clear and readable
Everything your pods need to know
Environment variables, application settings
All stored safe within the map
Ready when your containers start up
Filling every config gap
[Chorus]
From literal, from literal
Key equals value every time
From literal, from literal
Each setting on a separate line
Double dash from literal
That's the flag you need to know
Build your config piece by piece
Watch your application grow
[Outro]
Kubectl create configmap with your name
From literal makes it clear
Key equals value, repeat as needed
Your configuration's always here
6. Check CoreDNS
[Verse 1]
When your cluster's acting strange and DNS won't resolve
Pods can't find their services, problems to solve
Time to check the CoreDNS, the heart of naming flow
Two commands will guide you where the answers go
[Chorus]
Get pods first, then logs next
Kube-system namespace text
K-eight-s-app equals kube-dns
Check your CoreDNS, don't stress
Get pods first, then logs next
Find the pods that handle requests
[Verse 2]
Kubectl get pods in the kube-system space
Label selector finds the DNS embrace
K-eight-s-app equals kube-dns will show
Which pods are running, which are good to go
[Chorus]
Get pods first, then logs next
Kube-system namespace text
K-eight-s-app equals kube-dns
Check your CoreDNS, don't stress
Get pods first, then logs next
Find the pods that handle requests
[Bridge]
Once you see the pod names clear
Time for logs to make things appear
Same namespace, same label too
Kubectl logs will show what's true
Errors, warnings, startup pain
CoreDNS secrets logs explain
[Verse 3]
Logs command with the same label selector
Shows you errors like a truth detector
Configuration problems, network delays
CoreDNS logs will light the way
[Chorus]
Get pods first, then logs next
Kube-system namespace text
K-eight-s-app equals kube-dns
Check your CoreDNS, don't stress
Get pods first, then logs next
Find the pods that handle requests
[Outro]
Two commands to rule them all
When DNS begins to fall
Get the pods and get the logs
Clear the DNS naming fog
7. Describe an ingress (routes, backends, TLS)
[Verse 1]
When you need to peek inside your ingress setup
kubectl describe will show you what's up
Routes and rules all laid out clear
Backends and services appear
[Chorus]
Describe ingress, see the flow
Routes to backends, watch them go
TLS secrets, ports and names
Kubernetes routing, learn the game
[Verse 2]
Default backend catches all the rest
When no rules match, it handles the test
Host-based routing splits the traffic clean
Path-based rules keep URLs pristine
[Chorus]
Describe ingress, see the flow
Routes to backends, watch them go
TLS secrets, ports and names
Kubernetes routing, learn the game
[Bridge]
Annotations tell the story true
Load balancer configs coming through
Events section shows what went wrong
Status tells you if it's strong
[Verse 3]
TLS section holds your certificate data
Secret names and hosts, no need for beta
Port eighty and four-four-three
HTTP and HTTPS running free
[Chorus]
Describe ingress, see the flow
Routes to backends, watch them go
TLS secrets, ports and names
Kubernetes routing, learn the game
[Outro]
kubectl describe ingress by name
Master the routing, win the game
From frontend requests to backend calls
Ingress connects them through it all
8. List and inspect
[Verse 1]
When you need to find your config data stored
Kubectl get will show what's on board
List them all with configmaps command
See the names across your cluster land
[Chorus]
List and inspect, that's the way
Get describe and yaml display
List and inspect, check it twice
Config secrets, that's precise
Get the details, see it clear
List and inspect, data's here
[Verse 2]
Kubectl describe takes a name
Shows the details of the game
All the key-value pairs inside
Metadata that you cannot hide
[Chorus]
List and inspect, that's the way
Get describe and yaml display
List and inspect, check it twice
Config secrets, that's precise
Get the details, see it clear
List and inspect, data's here
[Verse 3]
Output yaml flag will show
Everything you need to know
Full structure in a readable way
Perfect format for your day
[Bridge]
ConfigMaps hold your settings tight
Secrets keep your passwords right
Three commands to rule them all
List inspect and never fall
[Chorus]
List and inspect, that's the way
Get describe and yaml display
List and inspect, check it twice
Config secrets, that's precise
Get the details, see it clear
List and inspect, data's here
[Outro]
From the cluster to your screen
List and inspect, keep it clean
Configuration management done
Kubectl makes it second to none
9. List services
[Verse 1]
When you need to see what's running in your cluster today
There's a simple command that will show you the way
Services are the bridge that connects all your pods
Kubectl get services reveals what you've got
[Chorus]
Get services, get svc, they're the same command
List them all, see them all, understand your planned
Network bridges, traffic guides, routing all your calls
Get services, get svc, Kubernetes shows them all
[Verse 2]
Type the full command or use the shorter way
Services or svc will display the same array
Names and types and cluster IPs too
External endpoints waiting there for you
[Chorus]
Get services, get svc, they're the same command
List them all, see them all, understand your planned
Network bridges, traffic guides, routing all your calls
Get services, get svc, Kubernetes shows them all
[Bridge]
Load balancer, node port, cluster IP inside
External name services, all the types you'll find
Age and selector, ports that they expose
Every service detail, that's how knowledge grows
[Verse 3]
From the command line you can see the full view
Which services are active and what they can do
The shorthand saves time when you're typing fast
Both commands give results that are built to last
[Chorus]
Get services, get svc, they're the same command
List them all, see them all, understand your planned
Network bridges, traffic guides, routing all your calls
Get services, get svc, Kubernetes shows them all
[Outro]
So remember the pattern, it's easy to see
Services or svc, both commands are key
Your cluster's connections are just one get away
List those services every single day
10. Get endpoints (which pods are backing a service)
[Verse 1]
When your service is running but pods seem to hide
You need to discover what's working inside
Behind every service there's endpoints to find
The pods that are ready to serve and reply
[Chorus]
Get endpoints, get endpoints
kubectl get endpoints service name
Get endpoints, get endpoints
Shows the pods that are backing your game
IP addresses and ports in a line
Ready pods that are working just fine
Get endpoints, get endpoints
That's the command you need to retain
[Verse 2]
Your service selector finds pods by their label
But which ones are healthy and ready and able
The endpoint controller keeps track of the state
Only ready pods make it through the gate
[Chorus]
Get endpoints, get endpoints
kubectl get endpoints service name
Get endpoints, get endpoints
Shows the pods that are backing your game
IP addresses and ports in a line
Ready pods that are working just fine
Get endpoints, get endpoints
That's the command you need to retain
[Bridge]
When traffic flows in through your service door
Endpoints decide where it goes and what for
No endpoints listed means no pods are ready
Check your deployment keep traffic steady
[Verse 3]
Debug your service when things go wrong
Use get endpoints to sing this song
Empty results mean your pods aren't there
Or readiness probes show they're not prepared
[Chorus]
Get endpoints, get endpoints
kubectl get endpoints service name
Get endpoints, get endpoints
Shows the pods that are backing your game
IP addresses and ports in a line
Ready pods that are working just fine
Get endpoints, get endpoints
That's the command you need to retain
[Outro]
Service name after endpoints command
Now you know where your ready pods stand
11. Test DNS resolution from inside the cluster
[Verse 1]
When your pods can't find each other in the night
And services seem hidden from their sight
There's a way to check if DNS is working right
From inside your cluster, bring the truth to light
Run a test pod with busybox in hand
One-three-six version, stable and so grand
Interactive terminal, then remove on command
DNS resolution, help us understand
[Chorus]
kubectl run dns-test, busybox one-three-six
Interactive, remove it, temporary fix
nslookup service-name, see if it resolves
Inside the cluster, mystery it solves
Test your DNS, test your DNS
From within the cluster, no need to guess
Test your DNS, test your DNS
Resolution working, cleaning up the mess
[Verse 2]
Sometimes short names fail but don't despair
Fully qualified domains show what's really there
Service dot namespace dot svc dot cluster dot local care
Complete the puzzle, DNS everywhere
Busybox container, lightweight and clean
Interactive flag lets you see the screen
Remove when finished, keeping cluster lean
Restart policy never, ephemeral machine
[Chorus]
kubectl run dns-test, busybox one-three-six
Interactive, remove it, temporary fix
nslookup service-name, see if it resolves
Inside the cluster, mystery it solves
Test your DNS, test your DNS
From within the cluster, no need to guess
Test your DNS, test your DNS
Resolution working, cleaning up the mess
[Bridge]
When debugging network issues late at night
This little test pod makes everything bright
From inside looking out, the perspective's right
DNS resolution brought into the light
[Chorus]
kubectl run dns-test, busybox one-three-six
Interactive, remove it, temporary fix
nslookup service-name, see if it resolves
Inside the cluster, mystery it solves
Test your DNS, test your DNS
From within the cluster, no need to guess
Test your DNS, test your DNS
Resolution working, cleaning up the mess
[Outro]
Now you know the secret, debugging made clear
Test from within when services disappear
DNS resolution, keep your cluster near
Busybox nslookup, the answer's here
12. Create from a file
[Verse 1]
When your config needs a home in Kubernetes land
There's a simple way to get it all planned
Take your properties file sitting on your drive
kubectl create will bring it alive
From file to cluster, data flows so clean
ConfigMap magic, best you've ever seen
Name your resource, point it to the source
Let Kubernetes handle it with gentle force
[Chorus]
From file creates the map you need
Config properties, plant the seed
Dash dash from file, that's the key
Name and path, now you're running free
From env file when environment calls
One command and you've got it all
Create ConfigMap, data in place
Kubernetes storage with perfect grace
[Verse 2]
Properties file with keys and values neat
Dot properties extension, configuration complete
Name your ConfigMap, something you'll remember
From file flag points to your dataember
When environment variables need their space
Dot env file puts them in their place
From env file flag does the trick
One command and your config sticks
[Chorus]
From file creates the map you need
Config properties, plant the seed
Dash dash from file, that's the key
Name and path, now you're running free
From env file when environment calls
One command and you've got it all
Create ConfigMap, data in place
Kubernetes storage with perfect grace
[Bridge]
kubectl create, the command starts
ConfigMap name, straight from the heart
From file or env file, choose your way
Data flows where pods can play
[Verse 3]
Two paths forward, both will serve you well
Properties or env, both have stories to tell
From file takes your config straight and true
From env file makes environment new
Name your maps with purpose and with care
Data living in the cluster's air
Pods will find them when the time is right
Configuration shining bright
[Chorus]
From file creates the map you need
Config properties, plant the seed
Dash dash from file, that's the key
Name and path, now you're running free
From env file when environment calls
One command and you've got it all
Create ConfigMap, data in place
Kubernetes storage with perfect grace
[Outro]
File to cluster, simple as can be
ConfigMap creation, you hold the key
From file, from env file, both ways shine
Kubernetes config, working fine
13. Create a generic secret
[Verse 1]
When your app needs private data stored away
Passwords and tokens that can't see the light of day
Kubernetes has a way to keep things concealed
With secrets that are properly sealed
[Chorus]
kubectl create secret generic name
from literal makes the claim
Password equals your secure string
That's the pattern that we sing
Generic secrets keep it safe
In the cluster's hidden space
kubectl create secret generic name
That's how we play the secret game
[Verse 2]
Start with kubectl and the create command
Secret generic helps you take a stand
Choose a name that makes sense to you
Then from literal will see you through
[Chorus]
kubectl create secret generic name
from literal makes the claim
Password equals your secure string
That's the pattern that we sing
Generic secrets keep it safe
In the cluster's hidden space
kubectl create secret generic name
That's how we play the secret game
[Bridge]
No more hardcoded passwords in your code
Let Kubernetes carry that heavy load
From literal flag will take your key
And store it securely for all to see
Well, not to see, that's the whole point
Keep those secrets out of joint
[Chorus]
kubectl create secret generic name
from literal makes the claim
Password equals your secure string
That's the pattern that we sing
Generic secrets keep it safe
In the cluster's hidden space
kubectl create secret generic name
That's how we play the secret game
[Outro]
S three cur three P at sign s s
That's a password we won't confess
But now you know the proper way
To store secrets night and day
14. Create TLS secret
[Verse 1]
When your audiobook needs protection tight
TLS secrets keep your data right
Certificate and key must work as one
kubectl create secret gets the job done
[Chorus]
Create TLS secret with a name so clear
Cert and key flags make encryption appear
Kubectl create secret TLS today
Cert equals crt and key shows the way
Name it well and files align
TLS protection by design
[Verse 2]
First you need your certificate file
TLS dot crt stored in your pile
Private key sits right beside
TLS dot key your trusted guide
[Chorus]
Create TLS secret with a name so clear
Cert and key flags make encryption appear
Kubectl create secret TLS today
Cert equals crt and key shows the way
Name it well and files align
TLS protection by design
[Bridge]
Audiobooks streaming safe and sound
Encrypted channels all around
Two files joined in secret form
Keeping data safe from harm
[Verse 3]
Choose a name that makes good sense
Something clear for reference
Cert flag points to your crt
Key flag sets your private key
[Chorus]
Create TLS secret with a name so clear
Cert and key flags make encryption appear
Kubectl create secret TLS today
Cert equals crt and key shows the way
Name it well and files align
TLS protection by design
[Outro]
TLS secrets guard your audiobook stream
Certificate and key the perfect team
Kubectl makes it simple true
Secure connections wait for you
15. Create docker registry secret
[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
16. Decode a secret value
[Verse 1]
When secrets hide behind the wall
Encoded data, can't read at all
Base sixty-four has locked it tight
But kubectl holds the key tonight
Get the secret by its name
Output format, play the game
JSON path will lead the way
To the data where it stays
[Chorus]
Decode decode, the secret's there
Pipeline it through to make it clear
Base sixty-four dash d will show
The password that you need to know
Decode decode, don't let it hide
The value's waiting there inside
[Verse 2]
First you get the secret store
Specify the name and nothing more
O flag for output, set it right
JSON path brings data to light
Dot data dot password is the trail
Through the structure without fail
Pipe symbol sends it on its way
To base sixty-four today
[Chorus]
Decode decode, the secret's there
Pipeline it through to make it clear
Base sixty-four dash d will show
The password that you need to know
Decode decode, don't let it hide
The value's waiting there inside
[Bridge]
Never store them in your Git
External vaults are where they sit
Vault or AWS will do
Azure Key Vault's good for you
External Secrets Operator
Makes your cluster so much greater
Encrypt at rest in etcd
Rotate them regularly
[Verse 3]
Immutable flag set to true
Stops the changes coming through
Performance boost for your cluster
No more secret data bluster
[Chorus]
Decode decode, the secret's there
Pipeline it through to make it clear
Base sixty-four dash d will show
The password that you need to know
Decode decode, don't let it hide
The value's waiting there inside
[Outro]
From encoded to the clear
The secret value will appear
Kubectl gets and base converts
The hidden password it preserves
17. List persistent volumes (cluster-wide)
[Verse 1]
In the cluster where our data lives
Storage needs a place to call its home
Persistent volumes are the gifts
That keep our files when pods must roam
When containers come and go away
The data stays another day
[Chorus]
kubectl get pv, that's the key
List them all for you and me
Persistent volumes cluster-wide
Storage resources you can't hide
Get pv, get pv, see them all
Available, bound, they stand tall
[Verse 2]
Each volume has a size to claim
Gigabytes or terabytes to store
Access modes define the game
ReadWriteOnce or maybe more
Status shows you what's in use
Bound or free, there's no excuse
[Chorus]
kubectl get pv, that's the key
List them all for you and me
Persistent volumes cluster-wide
Storage resources you can't hide
Get pv, get pv, see them all
Available, bound, they stand tall
[Bridge]
From the terminal you type
kubectl get pv tonight
See the names and see the class
Watch the storage status pass
Reclaim policy tells the tale
Delete or retain, without fail
[Verse 3]
Storage classes organize
Different types for different needs
SSD or traditional drives
Match the volume to your deeds
Age column shows how long they've been
Part of your Kubernetes scene
[Chorus]
kubectl get pv, that's the key
List them all for you and me
Persistent volumes cluster-wide
Storage resources you can't hide
Get pv, get pv, see them all
Available, bound, they stand tall
[Outro]
When you need to see your storage
kubectl get pv is your friend
Cluster-wide persistent volumes
Listed clearly end to end
18. List persistent volume claims (namespaced)
[Verse 1]
When your pods need storage that won't disappear
Persistent volumes keep your data here
But claims are how you ask for what you need
A namespace resource, that's the key indeed
[Chorus]
Get P-V-C, list them all today
Kubectl get pvc shows the namespace way
Add dash A flag when you need to see
Every claim across your cluster free
Get P-V-C, storage made so clear
Bound or pending, see what's really there
[Verse 2]
In your current namespace, the simple command
Shows the claims that help your workloads stand
Name and status, capacity and age
All the details written on the page
[Chorus]
Get P-V-C, list them all today
Kubectl get pvc shows the namespace way
Add dash A flag when you need to see
Every claim across your cluster free
Get P-V-C, storage made so clear
Bound or pending, see what's really there
[Bridge]
When you're troubleshooting storage woes
Check if claims are bound, that's how it goes
Cross all namespaces with the A flag bright
See the bigger picture, get it right
[Verse 3]
Some claims are waiting, some are bound tight
Some show errors, something's not quite right
Access modes tell you read and write
Size and storage class shine the light
[Chorus]
Get P-V-C, list them all today
Kubectl get pvc shows the namespace way
Add dash A flag when you need to see
Every claim across your cluster free
Get P-V-C, storage made so clear
Bound or pending, see what's really there
[Outro]
From local namespace to cluster wide
P-V-C commands are your storage guide
Remember the flags, remember the way
Get P-V-C saves the day
19. Describe a PVC (binding status, events)
[Verse 1]
When your audiobook won't start to play
And the storage seems to slip away
There's a command that shows the way
Kubectl describe will save the day
Check your PVC with just one line
See the binding status, is it fine?
Name it right and you will find
All the details you need to shine
[Chorus]
Describe PVC, check the state
Bound or pending, don't be late
Events will show you what went wrong
Storage dancing to this song
Describe PVC, make it right
Binding status shining bright
Your audiobook will play along
When storage sings the perfect song
[Verse 2]
Persistent Volume Claim's the key
To mount your books for all to see
But when it fails mysteriously
The describe command sets you free
Look for events at the bottom line
They tell the story every time
If volumes can't align just right
The events will bring it all to light
[Chorus]
Describe PVC, check the state
Bound or pending, don't be late
Events will show you what went wrong
Storage dancing to this song
Describe PVC, make it right
Binding status shining bright
Your audiobook will play along
When storage sings the perfect song
[Bridge]
Capacity and access modes
Storage class that fits your codes
Creation time and namespace too
All the info there for you
When binding fails or hangs around
In the events the cause is found
Insufficient storage space
Or wrong class in the wrong place
[Chorus]
Describe PVC, check the state
Bound or pending, don't be late
Events will show you what went wrong
Storage dancing to this song
Describe PVC, make it right
Binding status shining bright
Your audiobook will play along
When storage sings the perfect song
[Outro]
So when your imported books won't flow
Kubectl describe helps you know
PVC status tells the tale
Your audiobooks will never fail
Back to Home