As a recovering VMware architect, it took me a little while to grasp Kubernetes. And I noticed I’m not alone in this.. From developers on our own team who need to get fluent in Kubernetes fast to do their dev work, to IT generalists on the customer side who've spent a decade running vSphere and are now migrating off it as software is increasingly packaged as containers. Different people, same question: where do I actually start learning? They get the same non-answer when they look online. A paid course that regurgitates the docs. A certification path that goes too deep too fast.
A podcast list with no discernible information density. A "top resources" listicle with more links than anyone could click in a year (and most of them pointers to a corporate blog). None of that actually helps people grasp the key concepts of Kubernetes to help build the mental scaffolding so they can dive deep into specific topics. There are five pieces of scaffolding that help to build that mental model before diving into Kubernetes more deeply. Desired state and reconciliation. This is the one idea underneath every other behavior Kubernetes has.
You don't tell it to run a container, you declare that a container should exist, and something keeps checking reality against that declaration and correcting the gap, forever, without being asked. A rollout is this, just the desired state changing in controlled steps. If you don't have this one straight, everything else looks like a pile of separate features you have to memorize instead of one mechanism wearing different clothes. The control plane and worker split, and what "disposable" really means. This is the one your vSphere years actively work against you on.
An ESXi host that gets sick gets nursed, migrated off, patched, brought back. A Kubernetes node that gets sick gets replaced. Any healthy node can run any workload, so the system doesn't try to save the failing one, it just routes around it. That's not a minor implementation detail, it's a different relationship with the hardware underneath you, and if you carry the vSphere instinct of babying a specific box into a Kubernetes cluster, you'll spend a lot of energy protecting something the system was designed to let go of. The four networking layers, from a container out.