summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com>2017-09-26 09:17:55 -0700
committerGitHub <noreply@github.com>2017-09-26 09:17:55 -0700
commit5d96914f550f17faff599367e488b8c010ca0e22 (patch)
tree5d4d79e1e99650f83406bf72f07e52d9641f29dc
parentcfac9e3f82890c1311803bf2f14f021484b5e31a (diff)
parentc6ebe36240619955439bd2d215313661b7946771 (diff)
Merge pull request #1130 from gaocegege/fix-link
Automatic merge from submit-queue. . podaffinity.md: Fix a broken link
-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"}`