Hi to upgrade k3s this page says I can just run `curl sfL <h rancher-users #k3s

Title

square-coat-44873

12/21/2022, 10:56 PM

Hi, to upgrade k3s, this page says I can just run

curl -sfL <https://get.k3s.io> | sh -

Do I run this on each k3s server (master)? on each agent (worker)? Does this upgrade the underlying version of k8s as well (and all of the underlying tools, i.e. containerd, runc, …)? https://docs.k3s.io/upgrades/manual#upgrade-k3s-using-the-installation-script

btw, I like the conciseness of the docs. but might be useful to update the docs with a bit more info like this.

Okay, i was feeling a bit gutsy. I ran this command only on the master (I only have 1 in my setup). Then I ran the same install command that I used from original installation on each of the workers: curl -sfL https://get.k3s.io | K3S_URL=https://myserver:6443 K3S_TOKEN=mynodetoken sh -

this seemed to upgrade k3s and k8s levels.

gray-lawyer-73831

12/21/2022, 11:18 PM

Yep, that’s correct. You run it on each server node, then you run it on each agent node! And it does upgrade k8s and all the underlying components 👍

square-coat-44873

12/21/2022, 11:18 PM

ok, cool. thx for confirming! 👍🙏

creamy-pencil-82913

12/22/2022, 1:29 AM

k3s is kubernetes and all the underlying components 😉

square-coat-44873

12/22/2022, 1:30 AM

ok that’s what i was thinking, but wasn’t certain. thx for clarifying!

i guess its just packaged differently though, right?

i noticed many of the k8s components run inside the k3s server

creamy-pencil-82913

12/22/2022, 1:30 AM

every disto does things differently. We just happen to include a bunch of stuff that some other distro don’t (container runtime, datastore, loadbalancer controller, stub cloud controller), and run most of it all in a single process to take advantage of shared caches.

5 Views