From 6e3af1055c2a4ad782a299ee9cca9e4f4e7c56ca Mon Sep 17 00:00:00 2001 From: TigerXu Date: Tue, 15 Aug 2017 01:12:21 +0800 Subject: [PATCH] Update multiple-zones.md (#4819) * Update multiple-zones.md update link * Update multiple-zones.md --- docs/admin/multiple-zones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/multiple-zones.md b/docs/admin/multiple-zones.md index 8963259213..095e9bc389 100644 --- a/docs/admin/multiple-zones.md +++ b/docs/admin/multiple-zones.md @@ -11,7 +11,7 @@ title: Running in Multiple Zones Kubernetes 1.2 adds support for running a single cluster in multiple failure zones (GCE calls them simply "zones", AWS calls them "availability zones", here we'll refer to them as "zones"). This is a lightweight version of a broader Cluster Federation feature (previously referred to by the affectionate -nickname ["Ubernetes"](https://git.k8s.io/community/contributors/design-proposals/federation.md)). +nickname ["Ubernetes"](https://github.com/kubernetes/community/blob/{{page.githubbranch}}/contributors/design-proposals/federation.md)). Full Cluster Federation allows combining separate Kubernetes clusters running in different regions or cloud providers (or on-premises data centers). However, many