Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix typo #10168

Merged
merged 3 commits into from
Sep 10, 2018
Merged

fix typo #10168

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d56474
fix typo
Aug 31, 2018
0724911
addressing comments.
Sep 1, 2018
d143bd0
Update setup-ha-etcd-with-kubeadm.md
Sep 3, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions content/en/docs/setup/independent/setup-ha-etcd-with-kubeadm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
---
reviewers:
- sig-cluster-lifecycle
title: Set up a Highly Availabile etcd Cluster With kubeadm
title: Set up a High Availability etcd cluster with kubeadm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mauilion 👋 For future reference: "High Availability" is lower case: high availability, highly available. See other uses in this article for examples.

/cc @Bradamant3

content_template: templates/task
weight: 60
---

{{% capture overview %}}

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
becoming unavailable. This task walks through the process of creating a highly
available etcd cluster of three members that can be used as an external etcd
becoming unavailable. This task walks through the process of creating a high
availability etcd cluster of three members that can be used as an external etcd
when using kubeadm to set up a kubernetes cluster.

{{% /capture %}}
Expand Down Expand Up @@ -108,7 +108,7 @@ this example.
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
`/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
generated the configuration files for kubeadm).
Expand Down