Remove outdated reference to disabling Traefik

This commit is contained in:
Catherine Luse
2020-03-31 13:34:55 -07:00
parent a7e8ca8720
commit 59bb8dd344
2 changed files with 5 additions and 1 deletions
@@ -82,6 +82,10 @@ When a K3s cluster is imported, Rancher will recognize it as K3s, and the Ranche
- The ability to configure the maximum number of nodes that will be upgraded concurrently
- The ability to see a read-only version of the K3s cluster's configuration arguments and environment variables used to launch each node in the cluster.
### Configuring K3s Cluster Upgrades
> **Important:** Before upgrading the Kubernetes version of a high-availability K3s cluster, back up the database in whichever way is recommended by the relational database provider. If the upgrade fails, restore the cluster from the snapshot.
The **concurrency** is the maximum number of nodes that are permitted to be unavailable during an upgrade. If number of unavailable nodes is larger than the **concurrency,** the upgrade will fail. If an upgrade fails, you may need to repair or remove failed nodes before the upgrade can succeed.
- **Controlplane concurrency:** The maximum number of server nodes to upgrade at a single time; also the maximum unavailable server nodes
@@ -35,7 +35,7 @@ The steps to set up the Kubernetes cluster differ depending on whether you are u
### 1. Install Kubernetes and Set up the K3s Server
When running the command to start the K3s Kubernetes API server, you will pass in two options: one option to use the external datastore that you set up earlier, and one to prevent K3s from deploying Traefik, which is the default ingress in K3s. You need to disable Traefik because Rancher will use NGINX as the ingress to allow external traffic into the cluster.
When running the command to start the K3s Kubernetes API server, you will pass in an option to use the external datastore that you set up earlier.
1. Connect to one of the Linux nodes that you have prepared to run the Rancher server.
1. On the Linux node, run this command to start the K3s server and connect it to the external datastore: