summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Danese <mikedanese@gmail.com>2015-07-10 12:51:35 -0700
committerMike Danese <mikedanese@gmail.com>2015-07-10 12:51:35 -0700
commit3a38ce4217962abf1ebd37e08ea51c5c857de70e (patch)
treef556712a166ea9495c5b8afe64e6d9fa84ebb149
parent31aa6f84d4568893bde008d20eb0551eea228a68 (diff)
fix verify gendocs
-rw-r--r--cherry-picks.md3
-rw-r--r--scheduler_algorithm.md2
2 files changed, 4 insertions, 1 deletions
diff --git a/cherry-picks.md b/cherry-picks.md
index b6669110..5fbada99 100644
--- a/cherry-picks.md
+++ b/cherry-picks.md
@@ -30,3 +30,6 @@ conflict***.
Now that we've structured cherry picks as PRs, searching for all cherry-picks
against a release is a GitHub query: For example,
[this query is all of the v0.21.x cherry-picks](https://github.com/GoogleCloudPlatform/kubernetes/pulls?utf8=%E2%9C%93&q=is%3Apr+%22automated+cherry+pick%22+base%3Arelease-0.21)
+
+
+[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/cherry-picks.md?pixel)]()
diff --git a/scheduler_algorithm.md b/scheduler_algorithm.md
index dbd0d7cd..f353a4ed 100644
--- a/scheduler_algorithm.md
+++ b/scheduler_algorithm.md
@@ -30,7 +30,7 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl
- `CalculateSpreadPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on the same node.
- `CalculateAntiAffinityPriority`: Spread Pods by minimizing the number of Pods belonging to the same service on nodes with the same value for a particular label.
-The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](../../plugin/pkg/scheduler/algorithm/priorities). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](../../plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [docs/devel/scheduler.md](../../docs/devel/scheduler.md) for how to customize).
+The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](../../plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](../../plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [docs/devel/scheduler.md](../../docs/devel/scheduler.md) for how to customize).
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/scheduler_algorithm.md?pixel)]()