summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCe Gao <ce.gao@outlook.com>2017-09-26 18:55:48 +0800
committerCe Gao <ce.gao@outlook.com>2017-09-26 18:55:48 +0800
commitc6ebe36240619955439bd2d215313661b7946771 (patch)
tree04e0d758c0935050f8eb11f29f9f39a07b10f639
parent2920f3430d8df517655ca9c79a89f4eb8922768e (diff)
podaffinity.md: Fix a broken link
Signed-off-by: Ce Gao <ce.gao@outlook.com>
-rw-r--r--contributors/design-proposals/scheduling/podaffinity.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/scheduling/podaffinity.md b/contributors/design-proposals/scheduling/podaffinity.md
index 9291b8b9..24930f96 100644
--- a/contributors/design-proposals/scheduling/podaffinity.md
+++ b/contributors/design-proposals/scheduling/podaffinity.md
@@ -313,7 +313,7 @@ scheduler to not put more than one pod from S in the same zone, and thus by
definition it will not put more than one pod from S on the same node, assuming
each node is in one zone. This rule is more useful as PreferredDuringScheduling
anti-affinity, e.g. one might expect it to be common in
-[Cluster Federation](../../docs/proposals/federation.md) clusters.)
+[Cluster Federation](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/federation/federation.md) clusters.)
* **Don't co-locate pods of this service with pods from service "evilService"**:
`{LabelSelector: selector that matches evilService's pods, TopologyKey: "node"}`