Documented default SUC deployment with Rancher k3s upgrades (#3499)

* Documented default SUC deployment w/k3s upgrades

* Revised wording on k3s upgrades
This commit is contained in:
Jen Travinski
2021-09-10 16:21:46 -04:00
committed by GitHub
parent ca22e20ef7
commit 4a9ff6467b
@@ -24,14 +24,19 @@ For more details on the design and architecture of the system-upgrade-controller
- [system-upgrade-controller](https://github.com/rancher/system-upgrade-controller)
- [k3s-upgrade](https://github.com/rancher/k3s-upgrade)
To automate upgrades in this manner you must:
To automate upgrades in this manner, you must do the following:
1. Install the system-upgrade-controller into your cluster
1. Configure plans
>**Note:** Users can and should use Rancher to upgrade their K3s cluster if Rancher is managing it.
>
> * If you choose to use Rancher to upgrade, the following steps below are taken care of for you.
> * If you choose not to use Rancher to upgrade, you must use the following steps below to do so.
### Install the system-upgrade-controller
The system-upgrade-controller can be installed as a deployment into your cluster. The deployment requires a service-account, clusterRoleBinding, and a configmap. To install these components, run the following command:
The system-upgrade-controller can be installed as a deployment into your cluster. The deployment requires a service-account, clusterRoleBinding, and a configmap. To install these components, run the following command:
```
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.6.2/system-upgrade-controller.yaml
```