diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-09-16 09:05:34 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-16 09:05:34 -0700 |
| commit | ecea4de3da9905b593aa98f1bb3420cdebab92d1 (patch) | |
| tree | 2dca3d2a513cc98bc013ef0f2d38c652e892948d | |
| parent | 691d510be42187e5f086a0ac927e10aa77aea18a (diff) | |
| parent | 830891ae4d6149388f5d014077a6a474663dcff4 (diff) | |
Merge pull request #1079 from budhrg/master
Automatic merge from submit-queue
Fix broken link for federation/federation proposal
| -rw-r--r-- | contributors/design-proposals/federation/federation-phase-1.md | 2 |
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 |