Difference between revisions of "Kubernetes/Scheduling"
Jump to navigation
Jump to search
(Created page with "Default scheduler rules: # Identify if a node has adequate hardware resources # Check if a node is running out of resources. check for memory or disk pressure conditions # Che...") |
|||
Line 1: | Line 1: | ||
Default scheduler rules | = Default scheduler rules= | ||
# Identify if a node has adequate hardware resources | # Identify if a node has adequate hardware resources | ||
# Check if a node is running out of resources. check for memory or disk pressure conditions | # Check if a node is running out of resources. check for memory or disk pressure conditions | ||
Line 9: | Line 9: | ||
# Check if a pod or a node affinity rules and checking if scheduling the pod would break these rules | # Check if a pod or a node affinity rules and checking if scheduling the pod would break these rules | ||
# If there is more than one node could schedule a pod, the scheduler priorities the nodes and choose the best one. If they have the same priority it chooses in round-robin fashion. | # If there is more than one node could schedule a pod, the scheduler priorities the nodes and choose the best one. If they have the same priority it chooses in round-robin fashion. | ||
= Label nodes = | |||
= Resources = | = Resources = | ||
*[https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ Assigning a Pod to a Node] | *[https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ Assigning a Pod to a Node] | ||
*[https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity Pod and Node Affinity Rules] | *[https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity Pod and Node Affinity Rules] |
Revision as of 07:56, 19 July 2019
Default scheduler rules
- Identify if a node has adequate hardware resources
- Check if a node is running out of resources. check for memory or disk pressure conditions
- Check if a pod schedule is scheduled to a node by a name
- Check if a node has a label matching node selector in a pod spec
- Check if a pod is requesting to bound to a specific host port and if so, does the node have that port available
- Check if a pod is requesting a certain type of volume be mounted and if other pods are using the same volume
- Check if a pod tolerates taints of the node, eg. master nodes is tainted with "noSchedule"
- Check if a pod or a node affinity rules and checking if scheduling the pod would break these rules
- If there is more than one node could schedule a pod, the scheduler priorities the nodes and choose the best one. If they have the same priority it chooses in round-robin fashion.