Why Kubernetes schedules a pods to a node which is marked as "unschedulable" in Red Hat Atomic Host ?
Issue
- Why Kubernetes schedules pods to a node which is marked as "unschedulable" in Red Hat Atomic Host ?
Example
1. Mark the node as unschedulable
kubectl update nodes node1.example.com --patch='{"apiVersion": "v1beta3", "spec": {"unschedulable": true}}'
2. Verify the update
[root@master Atomic]$ kubectl get nodes
NAME LABELS STATUS
node1.example.com Unschedulable name=node1.example.com Ready
node2.example.com Schedulable dc=IST,name=node2.example.com Ready
3. Create a pod and check where the pod was scheduled
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS
188ae336-2b44-11e5-93c0-5254009e2c8a 10.20.54.10 db dbforweb node1.example.com/ name=db,selectorname=db Running
Environment
- Red Hat Enterprise Linux Atomic Host 7.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
