summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorClinton Yeboah <clintonyeb@gmail.com>2021-11-11 17:21:51 -0500
committerClinton Yeboah <clintonyeb@gmail.com>2021-11-11 17:21:51 -0500
commitaf9c50f4d8a1fa5bb167efd2422081dde980cdcd (patch)
tree186b250a6a293c79985d5c5bd1a2c876e91177f8
parent24f87a099f5cd0c89e6fdf1ec18bbc0ba81263cd (diff)
fixes broken link with scheduling documentation
-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