Skip to content

Commit cebf1ae

Browse files
committed
Add instruction to deploy system-upgrade-controller CRD
1 parent d051e9a commit cebf1ae

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/upgrades/automated.md

+7
Original file line numberDiff line numberDiff line change
@@ -43,12 +43,19 @@ When attempting to upgrade to a new version of K3s, the [Kubernetes version skew
4343
:::
4444

4545
### Install the system-upgrade-controller
46+
4647
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:
48+
4749
```bash
4850
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/system-upgrade-controller.yaml
4951
```
5052
The controller can be configured and customized via the previously mentioned configmap, but the controller must be redeployed for the changes to be applied.
5153

54+
To be able to apply plans, the system-upgrade-controller CRD has to be deployed:
55+
56+
```bash
57+
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/latest/download/crd.yaml
58+
```
5259

5360
### Configure plans
5461
It is recommended you create at least two plans: a plan for upgrading server (control-plane) nodes and a plan for upgrading agent nodes. You can create additional plans as needed to control the rollout of the upgrade across nodes. Once the plans are created, the controller will pick them up and begin to upgrade your cluster.

0 commit comments

Comments
 (0)