kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix broken links to /admin/multiple-zones (#9193)

This commit is contained in:
Luc Perkins 2018-06-25 22:18:52 -07:00 committed by k8s-ci-robot
parent 0f6fbe42c8
commit 755c3340ce
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/blog/_posts/2017-02-00-Highly-Available-Kubernetes-Clusters.md
View File

@ -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/)):
``` ```

2
content/en/docs/concepts/workloads/pods/disruptions.md
View File

@ -76,7 +76,7 @@ and [stateful](/docs/tasks/run-application/run-replicated-stateful-application/)
spread applications across racks (using spread applications across racks (using
[anti-affinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature)) [anti-affinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature))
or across zones (if using a 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 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 no voluntary disruptions at all. However, your cluster administrator or hosting provider

2
content/en/docs/tasks/administer-cluster/highly-available-master.md
View File

@ -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. * 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 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. * 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. As a result, both replicas are needed and a failure of any replica turns cluster into majority failure state.

2
data/setup.yml
View File

@ -134,7 +134,7 @@ toc:
path: /docs/admin/cluster-large/ path: /docs/admin/cluster-large/
- title: Running in Multiple Zones - title: Running in Multiple Zones
path: /docs/admin/multiple-zones/ path: /docs/setup/multiple-zones/
- title: Building High-Availability Clusters - title: Building High-Availability Clusters
path: /docs/admin/high-availability/building/ path: /docs/admin/high-availability/building/