public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

spelling fixes and remove disable-agent

Browse Source
This commit is contained in:
David Nuzik
2019-10-16 11:19:25 -07:00
parent 8c6918c758
commit 3342500740
4 changed files with 3 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/k3s/latest/en/advanced/_index.md
-3
View File
@@ -36,9 +36,6 @@ INFO[2019-01-22T15:16:20.541049100-07:00] Run: k3s kubectl
The output will likely be much longer as the agent will create a lot of logs. By default the server
will register itself as a node (run the agent).
It is common and almost required these days that the control plane be part of the cluster.
To disable the agent when running the server use the `--disable-agent` flag, the agent can then be run as a separate process.
Alpine Linux
------------
content/k3s/latest/en/installation/ha/_index.md
+1 -1
View File
@@ -23,7 +23,7 @@ Following the [Node Requirements]({{< baseurl >}}/k3s/latest/en/installation/nod
On the first machine, run the following command to install k3s and connect it to the database.
>**Note:** You may wish to taint the master nodes. They will run the kubelet by default and be scheduleable. You can only add node labels and taints during the install process. If you wish to do this, use the `--node-taint` flag. For example `--node-taint key1=value1:NoExecute` the folllowing examples do not include this flag.
>**Note:** You may wish to taint the master nodes. They will run the kubelet by default and be scheduleable. You can only add node labels and taints during the install process. If you wish to do this, use the `--node-taint` flag. For example `--node-taint key1=value1:NoExecute` the following examples do not include this flag.
```
curl -fL https://get.k3s.io | sh -s - server --storage-endpoint='postgres://username:password@hostname:5432/dbname' --bootstrap-save
content/k3s/latest/en/installation/node-requirements/_index.md
+1 -1
View File
@@ -17,7 +17,7 @@ k3s should run on just about any flavor of Linux. However, k3s is tested on the
## Hardware
Hardware requirements scale based on the size of your deployments. Minimum recommenedations are outlined here.
Hardware requirements scale based on the size of your deployments. Minimum recommendations are outlined here.
* RAM: 512MB Minimum
* CPU: 1 Minimum
content/k3s/latest/en/quick-start/_index.md
+1 -1
View File
@@ -3,7 +3,7 @@ title: "Quick-Start Guide"
weight: 1
---
>**Note:** The intent of this guide is to quickly launch a cluster that you can use to evaluate k3s. This guide is not intended for production environments. Production environments should utilize a High-Availability solutuion. The [installation options](../installation) section covers in greater detail how k3s can be setup.
>**Note:** The intent of this guide is to quickly launch a cluster that you can use to evaluate k3s. This guide is not intended for production environments. Production environments should utilize a High-Availability solution. The [installation options](../installation) section covers in greater detail how k3s can be setup.
Install Script
--------------