From 755c3340cee188e41906399ab1f9342700915e5c Mon Sep 17 00:00:00 2001 From: Luc Perkins Date: Mon, 25 Jun 2018 22:18:52 -0700 Subject: [PATCH] Fix broken links to /admin/multiple-zones (#9193) --- .../_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md | 2 +- content/en/docs/concepts/workloads/pods/disruptions.md | 2 +- .../en/docs/tasks/administer-cluster/highly-available-master.md | 2 +- data/setup.yml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/blog/_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md b/content/en/blog/_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md index df5358332e..d042699192 100644 --- a/content/en/blog/_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md +++ b/content/en/blog/_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md @@ -38,7 +38,7 @@ $ KUBE\_GCE\_ZONE=europe-west1-b ./cluster/kube-up.sh -Now, we will add two additional pools of worker nodes, each of three nodes, in zones europe-west1-c and europe-west1-d (more details on adding pools of worker nodes can be find [here](http://kubernetes.io/docs/admin/multiple-zones/)): +Now, we will add two additional pools of worker nodes, each of three nodes, in zones europe-west1-c and europe-west1-d (more details on adding pools of worker nodes can be find [here](http://kubernetes.io/docs/setup/multiple-zones/)): ``` diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 86f04ee7a8..1a620c9b75 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -76,7 +76,7 @@ and [stateful](/docs/tasks/run-application/run-replicated-stateful-application/) spread applications across racks (using [anti-affinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature)) or across zones (if using a -[multi-zone cluster](/docs/admin/multiple-zones).) +[multi-zone cluster](/docs/setup/multiple-zones).) The frequency of voluntary disruptions varies. On a basic Kubernetes cluster, there are no voluntary disruptions at all. However, your cluster administrator or hosting provider diff --git a/content/en/docs/tasks/administer-cluster/highly-available-master.md b/content/en/docs/tasks/administer-cluster/highly-available-master.md index 5427e198e1..6e9bd16f68 100644 --- a/content/en/docs/tasks/administer-cluster/highly-available-master.md +++ b/content/en/docs/tasks/administer-cluster/highly-available-master.md @@ -108,7 +108,7 @@ $ KUBE_GCE_ZONE=replica-zone KUBE_REPLICATE_EXISTING_MASTER=true ./cluster/kube- * Try to place master replicas in different zones. During a zone failure, all masters placed inside the zone will fail. To survive zone failure, also place nodes in multiple zones -(see [multiple-zones](/docs/admin/multiple-zones/) for details). +(see [multiple-zones](/docs/setup/multiple-zones/) for details). * Do not use a cluster with two master replicas. Consensus on a two-replica cluster requires both replicas running when changing persistent state. As a result, both replicas are needed and a failure of any replica turns cluster into majority failure state. diff --git a/data/setup.yml b/data/setup.yml index f09b31417d..5a99ed9e55 100644 --- a/data/setup.yml +++ b/data/setup.yml @@ -134,7 +134,7 @@ toc: path: /docs/admin/cluster-large/ - title: Running in Multiple Zones - path: /docs/admin/multiple-zones/ + path: /docs/setup/multiple-zones/ - title: Building High-Availability Clusters path: /docs/admin/high-availability/building/