summaryrefslogtreecommitdiff
path: root/contributors/devel/scheduler_algorithm.md
diff options
context:
space:
mode:
authorguineveresaenger <guineveresaenger@gmail.com>2017-11-03 16:55:51 -0700
committerguineveresaenger <guineveresaenger@gmail.com>2017-11-03 16:55:51 -0700
commita6dcf8678b5c3febaacf079b28174b4a2cbd88e2 (patch)
tree913bdbfb61d604ca9543955b861970e02996a5a2 /contributors/devel/scheduler_algorithm.md
parentb41c258f983f6a0ecb49a169a61673a1017639f8 (diff)
removed autogenerated munge analytics from files
Diffstat (limited to 'contributors/devel/scheduler_algorithm.md')
-rw-r--r--contributors/devel/scheduler_algorithm.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/contributors/devel/scheduler_algorithm.md b/contributors/devel/scheduler_algorithm.md
index dc98fe5e..1d3eb418 100644
--- a/contributors/devel/scheduler_algorithm.md
+++ b/contributors/devel/scheduler_algorithm.md
@@ -38,7 +38,3 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl
The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/HEAD/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](http://releases.k8s.io/HEAD/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 [scheduler.md](scheduler.md) for how to customize).
-
-<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
-[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/scheduler_algorithm.md?pixel)]()
-<!-- END MUNGE: GENERATED_ANALYTICS -->