From 18e66560173ac177f5359a428d3e865d278a11e0 Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Thu, 13 Apr 2017 13:42:16 -0700 Subject: [PATCH] design-proposals: fix link to multiple-schedulers --- contributors/design-proposals/metadata-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/metadata-policy.md b/contributors/design-proposals/metadata-policy.md index 57416f11b..f924bc658 100644 --- a/contributors/design-proposals/metadata-policy.md +++ b/contributors/design-proposals/metadata-policy.md @@ -10,7 +10,7 @@ or to reject creation/update of the object. In the future other actions might be supported, such as applying an initializer. The first use of `MetadataPolicy` will be to decide which scheduler should -schedule a pod in a [multi-scheduler](../proposals/multiple-schedulers.md) +schedule a pod in a [multi-scheduler](./multiple-schedulers.md) Kubernetes system. In particular, the policy will add the scheduler name annotation to a pod based on an annotation that is already on the pod that indicates the QoS of the pod. (That annotation was presumably set by a simpler