K3sup – bootstrap K3s over SSH in < 60s
github.com
K3sup – bootstrap K3s over SSH in < 60s
1–10 of 55 posts
Re: K3sup – bootstrap K3s over SSH in < 60s
#2Re: K3sup – bootstrap K3s over SSH in < 60s
#3Re: K3sup – bootstrap K3s over SSH in < 60s
#4I use official ‘ansible-playbook k3s.orchestration.site -i inventory.yml’ and it installs k3s over SSH and adds it into my kubectl context, all under 60s too.
Re: K3sup – bootstrap K3s over SSH in < 60s
#5We have been running into lot of issues at production with k3s. There I embarked on journey to writing a kubernetes compliant and equivalent platform in rust with the help of claude [1]. It is a fun little project for now, still figuring out stuff, idea is to keep it minimal and single binary every embedded including CNI, and support various runtimes like docker, containerd etc but also wasm, vms and also jvm.
Re: K3sup – bootstrap K3s over SSH in < 60s
#6You can pretty install it without ssh under 60s. The fun starts after it has been installed. We have been running into lot of issues at production with k3s. There I embarked on journey to writing a kubernetes compliant and equivalent platform in rust with the help of claude [1]. It is a fun little project for now, still figuring out stuff, idea is to keep it minimal and single binary every embedded including CNI, and…
Re: K3sup – bootstrap K3s over SSH in < 60s
#7Re: K3sup – bootstrap K3s over SSH in < 60s
#8You can pretty install it without ssh under 60s. The fun starts after it has been installed. We have been running into lot of issues at production with k3s. There I embarked on journey to writing a kubernetes compliant and equivalent platform in rust with the help of claude [1]. It is a fun little project for now, still figuring out stuff, idea is to keep it minimal and single binary every embedded including CNI, and…
Do you have a writeup what problems you ran into?
There were many issues. On top of my mind was, after a DR drill where in a VM was booted, node did not join the cluster. Apart from that bunch of issues due to etcd, longhorn.
Another major one was the CNI stopped work for a particular node. Garbage collection for images was another, we labelled the images, it would still remove then from the node.
Bunch of these kind of issues when our requirement is fairly straightforward. Therefore we are working towards a strip down version.
There is lot of operation complexity in general and most of us can do without.
Re: K3sup – bootstrap K3s over SSH in < 60s
#9Also, fun fact, k3sup is pronounced "ketchup" according to the README[0]
[0]: https://github.com/alexellis/k3sup/blob/master/README.md