I’ve tried out the K3s integration in Container Station. But I didn’t found a way to upgrade it to latest version. Current version is rancher/k3s:v1.21.1-k3s1 while latest version is v1.35.0-k3s1.
Anyone an idea to update it?
You can try to figure out which version will work using the internal autoupdater. I have tried from 1.33+ with no luck and abandoned it.
Sooooooo… I got bored and upgraded the k3s on qnap.
Use automated upgrade, but the max version is limited by capabilities of your kernel. For my machine it was v1.29.15+k3s1. After it my k3s do not start. My guess it is something to do with cgroups v2.
hope this will help 
Thanks, guess the only way to make K3s working is to use same version for nodes as used by Container Station. Which means I should use rancher/k3s:v1.21.1-k3s1, a version more than 3 years old. So I decided to change one of my agent nodes into server and install K9s next to it. K9s is a really fast dashboard running in a terminal. Everything runs very stable now and with latest K3s versions.
Nevertheless it is sad that QNAP doesn’t upgrade their stuff regularly.
Could you please share your intended use case for K3s? We would like to gain a deeper understanding of your requirements to better assist with your needs. Thank you!
Probably didnt understand what you mean, but kubernetes has at least compatibility of neighboring versions for client/server. And k3s is just a opinionated package of it.
It looks like you wish to have those nodes connected into one cluster as agents. I guess you will have much more luck(and ease of mind) if you run virtual machine/lxd of some minimal distribution and have much greater control over it.
Playing more with that idea, since I was not able to restore the native k3s after “autoupdate” sequence. I had created lxd container with latest ubuntu and, to my suprise, i was able to run version of 1.33.1.
Alpine linux lxd stubbornly failed with “cgroups v2 not found” for any version. I guess some part of the alpine distribution had required them. Will go for lookout for other linuxes.
ps. didnt get what you mean with mentioning the k9s. it is just a terminal ui for kuber, it has no relation to your server and will work with whatever you ask it to work with. Please clarify why you have mentioned it.
Hi, thanks for your reply. I’ve a few small servers running K3s which I use for WordPress stacks. With K3s is updating underlying hardware and/or operating system much easier as I can move the stacks from node to node.
I wanted to use the Kubernetes build in the NAS to have at least a dashboard and more easy deployment. But soon I ran into version problems with the nodes as stated in my message above.
ps1. as jrand0m wrote makes sense, indeed I want to have the nodes connected into one cluster as agents with the NAS as control unit. And it should be nice when there is a manual explaining how to set up such a cluster, including the way to avoid cgroups problems.
ps2. @jrand0m I mentioned K9s as I’m currently using it as a simple replacement for the Kubernetes dashboard build in Container Station of the NAS.