🧐 If Kubelet is only for worker nodes, then who runs the control plane components like the API server, scheduler, and controller-manager?
Reality: ❌ Kubelet runs on both worker and control plane nodes—but their roles differ!
✅ On Worker Nodes → Kubelet manages application pods, ensuring they run as per the scheduler’s instructions.
✅ On Control Plane Nodes → Kubelet manages static pods (like API server, scheduler, and controller-manager) by reading manifest files from /etc/kubernetes/manifests/.
🔹 The real twist? Control plane components are NOT scheduled like regular pods! Instead, Kubelet directly runs them as static pods, bypassing the API server entirely.
💡 Understanding this helps in debugging control plane failures and troubleshooting cluster issues. Next time someone says, “Kubelet is only for worker nodes,” you’ll know how to bust that myth!
Have you ever had to debug Kubelet behavior on a control plane node? Share your experience in the comments! 👇
