From 33425007407b07283f60c61dcb14f10c3c4c9164 Mon Sep 17 00:00:00 2001 From: David Nuzik Date: Wed, 16 Oct 2019 11:19:25 -0700 Subject: [PATCH] spelling fixes and remove disable-agent --- content/k3s/latest/en/advanced/_index.md | 3 --- content/k3s/latest/en/installation/ha/_index.md | 2 +- content/k3s/latest/en/installation/node-requirements/_index.md | 2 +- content/k3s/latest/en/quick-start/_index.md | 2 +- 4 files changed, 3 insertions(+), 6 deletions(-) diff --git a/content/k3s/latest/en/advanced/_index.md b/content/k3s/latest/en/advanced/_index.md index e3b2fddb454..f3b9ab92b68 100644 --- a/content/k3s/latest/en/advanced/_index.md +++ b/content/k3s/latest/en/advanced/_index.md @@ -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 ------------ diff --git a/content/k3s/latest/en/installation/ha/_index.md b/content/k3s/latest/en/installation/ha/_index.md index a5d605b2007..4fc2d5f6234 100644 --- a/content/k3s/latest/en/installation/ha/_index.md +++ b/content/k3s/latest/en/installation/ha/_index.md @@ -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 diff --git a/content/k3s/latest/en/installation/node-requirements/_index.md b/content/k3s/latest/en/installation/node-requirements/_index.md index 35a01cbcd68..2901694ba8f 100644 --- a/content/k3s/latest/en/installation/node-requirements/_index.md +++ b/content/k3s/latest/en/installation/node-requirements/_index.md @@ -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 diff --git a/content/k3s/latest/en/quick-start/_index.md b/content/k3s/latest/en/quick-start/_index.md index 23796e478ff..afcd3961ea4 100644 --- a/content/k3s/latest/en/quick-start/_index.md +++ b/content/k3s/latest/en/quick-start/_index.md @@ -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 --------------