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

fix typo (#10168) 

* fix typo

* addressing comments.

* Update setup-ha-etcd-with-kubeadm.md
This commit is contained in:
Duffie Cooley 2018-09-10 14:09:00 -07:00 committed by k8s-ci-robot
parent 068edf5c31
commit 4a15ba58b5
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/en/docs/setup/independent/setup-ha-etcd-with-kubeadm.md
View File

@ -1,7 +1,7 @@
--- ---
reviewers: reviewers:
- sig-cluster-lifecycle - sig-cluster-lifecycle
title: Set up a Highly Availabile etcd Cluster With kubeadm title: Set up a High Availability etcd cluster with kubeadm
content_template: templates/task content_template: templates/task
weight: 60 weight: 60
--- ---
@ -9,10 +9,10 @@ weight: 60
{{% capture overview %}} {{% capture overview %}}
Kubeadm defaults to running a single member etcd cluster in a static pod managed Kubeadm defaults to running a single member etcd cluster in a static pod managed
by the kubelet on the control plane node. This is not a highly available setup by the kubelet on the control plane node. This is not a high availability setup
as the etcd cluster contains only one member and cannot sustain any members as the etcd cluster contains only one member and cannot sustain any members
becoming unavailable. This task walks through the process of creating a highly becoming unavailable. This task walks through the process of creating a high
available etcd cluster of three members that can be used as an external etcd availability etcd cluster of three members that can be used as an external etcd
when using kubeadm to set up a kubernetes cluster. when using kubeadm to set up a kubernetes cluster.
{{% /capture %}} {{% /capture %}}
@ -108,7 +108,7 @@ this example.
If you already have a CA then the only action that is copying the CA's `crt` and If you already have a CA then the only action that is copying the CA's `crt` and
`key` file to `/etc/kubernetes/pki/etcd/ca.crt` and `key` file to `/etc/kubernetes/pki/etcd/ca.crt` and
`/etc/kubernetes/pki/etcd/ca.key`. After those files have been copied, please `/etc/kubernetes/pki/etcd/ca.key`. After those files have been copied, please
skip this step. proceed to "Create certificates for each member".
If you do not already have a CA then run this command on `$HOST0` (where you If you do not already have a CA then run this command on `$HOST0` (where you
generated the configuration files for kubeadm). generated the configuration files for kubeadm).