[Verse 1]
When you need to peek inside a node's state
kubectl describe will show you straight
Capacity tells you what's available to use
CPU and memory, the resources you can choose
Allocatable shows what pods can really claim
After system reserves, what's left in the game
[Chorus]
Capacity, allocatable, conditions, pods
Four key things that every node shows
Describe the node and you will see
The health and state of your machinery
Capacity, allocatable, conditions, pods
kubectl describe reveals the code
[Verse 2]
Node conditions tell you if it's running right
Ready, memory pressure, disk space tight
True or false for each condition type
Is your node healthy or not quite right
OutOfDisk, NetworkUnavailable too
These conditions tell you what your node can do
[Chorus]
Capacity, allocatable, conditions, pods
Four key things that every node shows
Describe the node and you will see
The health and state of your machinery
Capacity, allocatable, conditions, pods
kubectl describe reveals the code
[Bridge]
Pods section shows what's running there
Every container, every workload pair
Non-terminated pods are listed out
So you can see what it's all about
From system pods to your apps deployed
Check the node to see what's employed
[Verse 3]
Taints and tolerations, labels too
Architecture info to help you choose
Operating system, kernel version
All the details for your node's conversion
Events at bottom show what went wrong
A timeline of issues all along
[Chorus]
Capacity, allocatable, conditions, pods
Four key things that every node shows
Describe the node and you will see
The health and state of your machinery
Capacity, allocatable, conditions, pods
kubectl describe reveals the code
[Outro]
So when your cluster's acting strange
Use describe node to see the change
Four key sections, remember well
Your node's story they will tell