summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2021-11-22 07:27:08 -0800
committerGitHub <noreply@github.com>2021-11-22 07:27:08 -0800
commitb291e9a85c23641a03501a7185823070450025dc (patch)
tree40bebb886484955fac5289d512f2c132a36515a2 /contributors
parentee30cad67d16e27f08c52e1c42254f697fb7c655 (diff)
parentaf9c50f4d8a1fa5bb167efd2422081dde980cdcd (diff)
Merge pull request #6220 from clintonyeb/patch/fix_broken_ling_scheduling
Fixes broken URL in scheduler_algorithm for a deleted documentation
Diffstat (limited to 'contributors')
-rw-r--r--contributors/devel/sig-scheduling/scheduler_algorithm.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/sig-scheduling/scheduler_algorithm.md b/contributors/devel/sig-scheduling/scheduler_algorithm.md
index 15498ff3..e9a099a2 100644
--- a/contributors/devel/sig-scheduling/scheduler_algorithm.md
+++ b/contributors/devel/sig-scheduling/scheduler_algorithm.md
@@ -1,6 +1,6 @@
# 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.
+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 [scheduling_code_hierarchy_overview.md](scheduling_code_hierarchy_overview.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