I’m sure you’ve been there; by some twist of fate you’ve ended up working in a place where Kubernetes has appeared on the radar and now you’ve been dropped into a brave new world where pushing a code change involves something called a pod. More nomenclature. Shit just got real. While there’s no shortage of detailed and nuanced explorations of the plethora of resource types in both the official Kubernetes documentation and elsewhere on the internet, it’s hard (in words at least) to give a cohesive top-down view of how all these resources fit together, and why you’d choose one over the other.

With that in mind, I went and did a thing: (hope it helps somebody)