What Actually Happens When kube-scheduler Picks a Node (13 Stages Inside Kubernetes)
When a pod is created in Kubernetes, kube-scheduler assigns it to a node through a 13-stage process that includes filtering, scoring, and binding. The scheduler evaluates nodes based on resource availability, taints, affinity rules, and other constraints, eliminating unsuitable nodes early. If no node fits, preemption may occur to make room for high-priority pods. The final assignment is written to etcd, marking the pod as scheduled.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 225861) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } saiyam1814 Posted on Apr 29 • Originally published at blog.kubesimplify.com What Actually Happens When kube-scheduler Picks a Node (13 Stages Inside Kubernetes) #kubernetes #scheduler #internals #devops Your pod has just been written to etcd. The API server returned 201 Created. The pod exists. But spec.nodeName is still empty, and that is the entire reason this post exists. A pod with no node is not a real workload. It is a row in a database.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
