From 1203cf0bb163b71b198382b44e6e543cd3672f33 Mon Sep 17 00:00:00 2001 From: koukihai Date: Sat, 12 Dec 2020 22:23:04 +0100 Subject: [PATCH] [k3s] Update system-upgrade-controller to v0.6.2 --- content/k3s/latest/en/upgrades/automated/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/upgrades/automated/_index.md b/content/k3s/latest/en/upgrades/automated/_index.md index b5951bd3684..d61e541d5c3 100644 --- a/content/k3s/latest/en/upgrades/automated/_index.md +++ b/content/k3s/latest/en/upgrades/automated/_index.md @@ -33,7 +33,7 @@ To automate upgrades in this manner you must: ### 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: ``` -kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.4.0/system-upgrade-controller.yaml +kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/v0.6.2/system-upgrade-controller.yaml ``` The controller can be configured and customized via the previously mentioned configmap, but the controller must be redeployed for the changes to be applied.