diff options
| author | Tim Hockin <thockin@google.com> | 2015-07-17 15:35:41 -0700 |
|---|---|---|
| committer | Tim Hockin <thockin@google.com> | 2015-07-17 15:35:43 -0700 |
| commit | da3e5f056b57f17ae5234085a00e792adaa02d57 (patch) | |
| tree | 353b03851fb5203964fa04e0ed33c9391e27097f /scheduler_algorithm.md | |
| parent | 3e224d662c4fa605341cb6c57d98dcb143e6b2ae (diff) | |
Run gendocs
Diffstat (limited to 'scheduler_algorithm.md')
| -rw-r--r-- | scheduler_algorithm.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/scheduler_algorithm.md b/scheduler_algorithm.md index 791de7c4..e73e4f27 100644 --- a/scheduler_algorithm.md +++ b/scheduler_algorithm.md @@ -30,11 +30,13 @@ Documentation for other releases can be found at <!-- END STRIP_FOR_RELEASE --> <!-- END MUNGE: UNVERSIONED_WARNING --> + # Scheduler Algorithm in Kubernetes
For each unscheduled Pod, the Kubernetes scheduler tries to find a node across the cluster according to a set of rules. A general introduction to the Kubernetes scheduler can be found at [scheduler.md](scheduler.md). In this document, the algorithm of how to select a node for the Pod is explained. There are two steps before a destination node of a Pod is chosen. The first step is filtering all the nodes and the second is ranking the remaining nodes to find a best fit for the Pod.
## Filtering the nodes
+ The purpose of filtering the nodes is to filter out the nodes that do not meet certain requirements of the Pod. For example, if the free resource on a node (measured by the capacity minus the sum of the resource limits of all the Pods that already run on the node) is less than the Pod's required resource, the node should not be considered in the ranking phase so it is filtered out. Currently, there are several "predicates" implementing different filtering policies, including:
- `NoDiskConflict`: Evaluate if a pod can fit due to the volumes it requests, and those that are already mounted.
|