public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-18 10:55:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply requested fixes

Browse Source 
- Resolve all four comments posted by Catherine.
This commit is contained in:
David Nuzik
2019-11-12 12:16:39 -07:00
parent 8a836f724b
commit 20b777634a
4 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/k3s/latest/en/installation/_index.md
+3 -3
View File
@@ -9,15 +9,15 @@ This section contains instructions for installing k3s in various environments. P
* [Single Master Installation]({{< baseurl >}}/k3s/latest/en/installation/single-server/)
Install k3s on a single Linux host. Single master installs are recommended for development, test, or production environments where the cluster doesn't have to be readily available for a user-base and some down time is acceptible.
Install k3s on a single Linux host. Single master installs are recommended for development, test, or production environments where the cluster doesn't have to be readily available for a user-base and some downtime is acceptible.
* [High Availability (HA) Installation]({{< baseurl >}}/k3s/latest/en/installation/ha/)
Install k3s on two or more Linux hosts. High Availability installs are recommended for production environments that cannot tolerate any down time.
Install k3s on two or more Linux hosts. High Availability installs are recommended for production environments that cannot tolerate any downtime.
* [Air-Gap Installation]({{< baseurl >}}/k3s/latest/en/installation/airgap/)
Install k3s in an air-gapped environment. High Availability is recommended for production environments that cannot tolerate any down time.
Install k3s in an air-gapped environment. High Availability is recommended for production environments that cannot tolerate any downtime.
### Uninstalling
content/k3s/latest/en/installation/ha/_index.md
+4 -1
View File
@@ -38,7 +38,10 @@ On the first machine, run the following command to install k3s and connect it to
```
curl -fL https://get.k3s.io | sh -s - server --storage-endpoint='postgres://username:password@hostname:5432/dbname' --cluster-secret='mysecret' --bootstrap-save
```
Note: You may want to provide the database password and cluster-secret temporarily via a file or environment variable then destroy it or clear your bash history so the password is no longer exposed in plain text on the machine. The cluster-secret can contain any Unicode, although you should avoid single and double quotes and make sure the contents are terminal-friendly.
The cluster-secret can contain any Unicode, although you should avoid single and double quotes and make sure the contents are terminal-friendly.
Note: You may want to provide the database password and cluster-secret temporarily via a file or environment variable then destroy it or clear your bash history so the password is no longer exposed in plain text on the machine.
On the second machine, run the following command. Since we ran the first node with the `--bootstrap-save` flag the second and any additional machines will now automatically bootstrap HA.
content/k3s/latest/en/installation/node-requirements/_index.md
+1 -1
View File
@@ -7,7 +7,7 @@ k3s is very lightweight, but has some minimum requirements as outlined below.
Whether you're configuring a k3s cluster to run in a single-node or high-availability (HA) setup, each node running k3s should meet the following minimum requirements. You may need more resources to fit your needs.
## Pre-requisites
## Prerequisites
* Two nodes cannot have the same hostname. If all your nodes have the same hostname, pass `--node-name` or set `$K3S_NODE_NAME` with a unique name for each node you add to the cluster.
## Operating Systems
content/k3s/latest/en/quick-start/_index.md
+1 -1
View File
@@ -4,7 +4,7 @@ weight: 10
---
>**Note:** The intent of this guide is to quickly launch a cluster with default options. It is suitable for production environments if you can accept some downtime in production (e.g. on the Edge). A High-Availiability solution should be utilized if down time is not acceptible.
The [installation options](../installation) section covers in greater detail how k3s can be setup.
The [installation options](../installation) section covers in greater detail how k3s can be set up.
> New to Kubernetes? The official Kubernetes docs already have some great tutorials outlining the basics [here](https://kubernetes.io/docs/tutorials/kubernetes-basics/).