You're the host at a busy restaurant on a Friday night. A party of four walks in. Before you seat them, you run a quick checklist in your head: which tables are big enough, which ones are reserved, which section they asked for, and who they shouldn't be seated next to. If no table passes, they go on the waiting list.
That is the Kubernetes scheduler. Every pod is a party, every node is a table, and Pending is the waiting list. Once you see it this way, the event at the bottom of kubectl describe pod reads like a host explaining why there's no table for you. (I used AI tools to help research and draft this post, and checked the Kubernetes behavior against the official docs.)
The party size is what you reserved, not what you eat
When a party calls ahead for four, the host holds a four-top. It doesn't matter if two of them only order drinks. The table is held for four.
Pod requests work the same way.…