summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHarry Zhang <harryz@hyper.sh>2017-02-20 23:06:19 +0800
committerGitHub <noreply@github.com>2017-02-20 23:06:19 +0800
commitaf2e0676437438e3ca43f8e04e0d78b33fce8d68 (patch)
tree6ea8883a5e6c804ed6f6c614cdfcf7d3a5427f85
parent92eb24c1614c17f557ba121af540115fe8ce347b (diff)
parentcd8686581e563f8827d5a38fa2fff09b98a4f944 (diff)
Merge pull request #385 from guangxuli/design-proposals-readme-fix
fix the obvious link error
-rw-r--r--contributors/design-proposals/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/README.md b/contributors/design-proposals/README.md
index 85fc8245..aa4f866d 100644
--- a/contributors/design-proposals/README.md
+++ b/contributors/design-proposals/README.md
@@ -34,7 +34,7 @@ physical hosts.
A single Kubernetes cluster is not intended to span multiple availability zones.
Instead, we recommend building a higher-level layer to replicate complete
deployments of highly available applications across multiple zones (see
-[the multi-cluster doc](../admin/multi-cluster.md) and [cluster federation proposal](../proposals/federation.md)
+[the multi-cluster doc](https://kubernetes.io/docs/admin/multi-cluster/) and [cluster federation proposal](federation.md)
for more details).
Finally, Kubernetes aspires to be an extensible, pluggable, building-block OSS