From cf8b1bc6f7e0533975e2c07ca9a24a7d33cd0cbb Mon Sep 17 00:00:00 2001 From: Weibin Lin Date: Fri, 18 Aug 2017 04:40:00 +0800 Subject: [PATCH] Update index.md (#4999) fix typos --- docs/admin/high-availability/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/admin/high-availability/index.md b/docs/admin/high-availability/index.md index 5bff42541a..841f52b7d7 100644 --- a/docs/admin/high-availability/index.md +++ b/docs/admin/high-availability/index.md @@ -114,8 +114,8 @@ on a different node. ### Even more reliable storage -Of course, if you are interested in increased data reliability, there are further options which makes the place where etcd -installs it's data even more reliable than regular disks (belts *and* suspenders, ftw!). +Of course, if you are interested in increased data reliability, there are further options which make the place where etcd +installs its data even more reliable than regular disks (belts *and* suspenders, ftw!). If you use a cloud provider, then they usually provide this for you, for example [Persistent Disk](https://cloud.google.com/compute/docs/disks/persistent-disks) on the Google Cloud Platform. These @@ -126,7 +126,7 @@ Alternatively, you can run a clustered file system like Gluster or Ceph. Finall Regardless of how you choose to implement it, if you chose to use one of these options, you should make sure that your storage is mounted to each machine. If your storage is shared between the three masters in your cluster, you should create a different directory on the storage -for each node. Throughout these instructions, we assume that this storage is mounted to your machine in `/var/etcd/data` +for each node. Throughout these instructions, we assume that this storage is mounted to your machine in `/var/etcd/data`. ## Replicated API Servers @@ -164,7 +164,7 @@ in the file. At this point, you should have 3 apiservers all working correctly. If you set up a network load balancer, you should be able to access your cluster via that load balancer, and see traffic balancing between the apiserver instances. Setting up a load balancer will depend on the specifics of your platform, for example instructions for the Google Cloud -Platform can be found [here](https://cloud.google.com/compute/docs/load-balancing/) +Platform can be found [here](https://cloud.google.com/compute/docs/load-balancing/). Note, if you are using authentication, you may need to regenerate your certificate to include the IP address of the balancer, in addition to the IP addresses of the individual nodes.