summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBudh Ram Gurung <budhrg@users.noreply.github.com>2017-09-16 12:14:27 +0530
committerGitHub <noreply@github.com>2017-09-16 12:14:27 +0530
commit830891ae4d6149388f5d014077a6a474663dcff4 (patch)
tree2dca3d2a513cc98bc013ef0f2d38c652e892948d
parent691d510be42187e5f086a0ac927e10aa77aea18a (diff)
Fix broken link for federation/federation proposal
-rw-r--r--contributors/design-proposals/federation/federation-phase-1.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/federation/federation-phase-1.md b/contributors/design-proposals/federation/federation-phase-1.md
index 3aa16dd8..157b5668 100644
--- a/contributors/design-proposals/federation/federation-phase-1.md
+++ b/contributors/design-proposals/federation/federation-phase-1.md
@@ -7,7 +7,7 @@
In this document we propose a design for the “Control Plane” of
Kubernetes (K8S) federation (a.k.a. “Ubernetes”). For background of
this work please refer to
-[this proposal](../../docs/proposals/federation.md).
+[this proposal](federation.md).
The document is arranged as following. First we briefly list scenarios
and use cases that motivate K8S federation work. These use cases drive
the design and they also verify the design. We summarize the