Hi community, Perhaps, someone could provide useful information about the K3S manual upgrade together with Rancher. Case 1: Upgrade the K3S cluster that is running Rancher K3S version v1.24.9+k3s2 (0d4e64f7), go version go1.18.9 Rancher version: v2.7.6 In essence, this is a local Rancher cluster that was created separately from the Rancher. My first step was to create a K3S cluster and only after that, I installed Rancher in there. The original plan was to upgrade from 1.24 to 1.26, but will it suffice to just change the K3S binary on every VM to the new one? Case 2: Imported K3S cluster to Rancher k3s version v1.26.2+k3s1 (ea094d1d), go version go1.19.6 Rancher version: v2.7.6 Would be nice to upgrade to at least v1.27.x. I believe, here the process should be simpler, don't I? The aim of this message is to gather as much useful information as possible about potential problematic parts during the upgrade. Thanks in advance, P.S. If you know any straightforward and more effective ways to upgrade, I would be grateful.

Upgrading a rancher-managed cluster is as easy as editiong the cluster version from cluster managerment. HOWEVER it resulsts in some disruptions as k3s will restart. The cluster will be upgraded sequentially so there is still a working node.

Hi @powerful-librarian-10572, thank you for your reply, I much appreciate it. Actually, I'm not quite sure it is really a Rancher-managed cluster, because it was imported to the Rancher. Is the process different then?

A cluster becomes rancher-managed in my book as soon as rancher... manages it. That includes importing it. Maybe you're confusing it with the term "rancher-provisionned" ?

Yes, exactly, my bad :D

Just be mindful that i don't have experience with k3s clusters, only rke2. But it shouldnt be too different.

Got it, thanks a lot. So, will try to upgrade the cluster from the Rancher and provide some updates or feedback about the process. Perhaps, will be useful for someone else.