Most Pods reach a node through the scheduler: the Pod is created in the API with an empty spec.nodeName, the kube-scheduler picks a node and writes a binding, and that node's kubelet sees the Pod and starts it. Static Pods take a different path: the kubelet reads a manifest from its local staticPodPath directory and starts the Pod itself, then creates a mirror Pod in the API so you can see it.
Keep reading for free
Create a free StudyToCert account to read the rest of this lesson: 5 more sections, 3 key terms, a real-world example, an exam tip and self-check questions. Every lesson, lab and practice test is free with an account.