This message was deleted.
# k3sa
adamant-kite-43734
12/21/2022, 10:56 PMThis message was deleted.
s
square-coat-44873
12/21/2022, 10:58 PMbtw, I like the conciseness of the docs. but might be useful to update the docs with a bit more info like this.
square-coat-44873
12/21/2022, 11:15 PMOkay, 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 -
square-coat-44873
12/21/2022, 11:15 PMthis seemed to upgrade k3s and k8s levels.
g
gray-lawyer-73831
12/21/2022, 11:18 PMYep, 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 👍
s
square-coat-44873
12/21/2022, 11:18 PMok, cool. thx for confirming! 👍🙏
c
creamy-pencil-82913
12/22/2022, 1:29 AMk3s is kubernetes and all the underlying components 😉
s
square-coat-44873
12/22/2022, 1:30 AMok that’s what i was thinking, but wasn’t certain. thx for clarifying!
square-coat-44873
12/22/2022, 1:30 AMi guess its just packaged differently though, right?
square-coat-44873
12/22/2022, 1:30 AMi noticed many of the k8s components run inside the k3s server
c
creamy-pencil-82913
12/22/2022, 1:30 AMevery 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