5 ms·

you can run a kubernetes stack using k3s on a rpi stack within minutes. and it runs far better than all of these. https://blog.alexellis.io/test-drive-k3s-on-r

you can run a kubernetes stack using k3s on a rpi stack within minutes. and it runs far better than all of these. https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/ https://blog.alexellis.io/test-drive-k3s-on-raspberry-pi/ here's a live walkthrough - https://www.youtube.com/watch?v=DjpVtNjiXSU https://www.youtube.com/watch?v=DjpVtNjiXSU

detaro 7y ago
> and it runs far better than all of these. in what way?
- pas 7y ago
  k3s is a lightweight stripped down version of k8s, so it's smaller and faster, and tuned for more resource scarce environments, like an RPi.
rkachowski 7y ago
The author mentions the differences between k3s and micro k8s in the post and concludes that due to the quirks of k3s (subset of features running in a single binary) it's only really preferable if you want to run rancher.
- sandGorgon 7y ago
  That is not true. We have personally run k3s on AWS including cluster-scaler and spot instances. Last I checked, K3s is a fully certified distro of k8s.
breakingcups 7y ago
The author disagrees with you on both points, he asserts rpi's are way slower than "old" pc's and laptops and that MicroK8S is preferable over K3S. He actually provides arguments & benchmarks to back up those opinions. Could you do the same for yours?
- sandGorgon 7y ago
  Because I have run k3s in production with spot instances for a particular usecase on AWS with all cloud-y features. I don't want to make this into an anti stance, but we have totally loved the experience of using k3s. The way you use k3s generally is not like the way you read on this post. It's basically a single command experience with sane defaults (e.g traefik). The overall experience is very close to a single click experience...all the way to the cloud.
ClumsyPilot 7y ago
Hello, it's a fine tutorial, but what you stand stand up in minutes is mostly an empty cluster. You still need to deal with exposing your services to the network, etc. That's why I drew the layered diagram, and tried to cover installing what I consider basics services. You have to have them the cluster to be of practical use. Also, K3S is not just faster - storage solutions don't even work on K3S, or at least i don't see how you can make them work. If you try to install EdgeFS, it's integrated CSI driver requires you to deal with feature gates.

detaro 7y ago

> and it runs far better than all of these. in what way?

pas 7y ago
k3s is a lightweight stripped down version of k8s, so it's smaller and faster, and tuned for more resource scarce environments, like an RPi.

rkachowski 7y ago

The author mentions the differences between k3s and micro k8s in the post and concludes that due to the quirks of k3s (subset of features running in a single binary) it's only really preferable if you want to run rancher.

sandGorgon 7y ago
That is not true. We have personally run k3s on AWS including cluster-scaler and spot instances. Last I checked, K3s is a fully certified distro of k8s.

breakingcups 7y ago

The author disagrees with you on both points, he asserts rpi's are way slower than "old" pc's and laptops and that MicroK8S is preferable over K3S. He actually provides arguments & benchmarks to back up those opinions. Could you do the same for yours?

sandGorgon 7y ago
Because I have run k3s in production with spot instances for a particular usecase on AWS with all cloud-y features. I don't want to make this into an anti stance, but we have totally loved the experience of using k3s. The way you use k3s generally is not like the way you read on this post. It's basically a single command experience with sane defaults (e.g traefik). The overall experience is very close to a single click experience...all the way to the cloud.

ClumsyPilot 7y ago

Hello, it's a fine tutorial, but what you stand stand up in minutes is mostly an empty cluster. You still need to deal with exposing your services to the network, etc. That's why I drew the layered diagram, and tried to cover installing what I consider basics services. You have to have them the cluster to be of practical use. Also, K3S is not just faster - storage solutions don't even work on K3S, or at least i don't see how you can make them work. If you try to install EdgeFS, it's integrated CSI driver requires you to deal with feature gates.