Resolve nitpicks / wordage in a couple of areas

- node-requirements "set" env var, not "pass"
- single-server remove duplicate "specific" word
- possibly some other minor tweaks
This commit is contained in:
David Nuzik
2019-11-11 16:25:52 -07:00
parent f45ceddfe5
commit 4aa6e14179
2 changed files with 2 additions and 3 deletions
@@ -8,7 +8,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
* Two nodes cannot have the same hostname. If all your nodes have the same hostname, pass `--node-name` or `$K3S_NODE_NAME` with a unique name for each node you add to the cluster.
* 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
@@ -14,8 +14,7 @@ k3s is easy to install. To install the latest version, simply run:
curl -sfL https://get.k3s.io | sh -
```
The install script will attempt to download the latest release. To specify a specific
version for download we can use the `INSTALL_K3S_VERSION` environment variable. For example:
The install script will attempt to download the latest release. To specify a version for download we can use the `INSTALL_K3S_VERSION` environment variable. For example:
```sh
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=vX.Y.Z-rc1 sh -
```