3 ms·

FYI, if you're looking to deploy a hobbyist/side-project Kubernetes cluster I'd highly recommend k3s [1] - it's a lightweight certified distribution, and is rid

by odensc 7y ago

FYI, if you're looking to deploy a hobbyist/side-project Kubernetes cluster I'd highly recommend k3s [1] - it's a lightweight certified distribution, and is ridiculously easy to set up. I haven't needed to do any maintenance besides the periodic update. It also works fine for production in my experience, I have a mildly popular website running on a 4GB VPS with it and haven't had any issues related to k3s itself. [1]: https://k3s.io/ https://k3s.io/

nullwarp 7y ago
Amen to that, after avoiding kubernetes at home for so long (run a quite a lot of clusters at work in production and while not a nightmare, it is a lot of work) - I've now moved most of my self-hosted stuff to k3s. It's been a joy to work with. We're even looking at starting to migrate most of our edge deployments to k3s as well. Really really awesome piece of work by Rancher.
- devit 7y ago
  What is the advantage compared to the traditional method of getting a single Linux system or VM, installing the needed packages via apt/yum, rsyncing over your code (if any) and installing systemd units for anything that needs to run all the time or scheduled? Are Helm charts easier to use or more prevalent than distribution packages?
ukd1 7y ago
Similar, and probably slightly easier from my experience, plus supports things like clustering and easily managing service, is microk8s[1] from canonical. [1]: https://microk8s.org https://microk8s.org
- tuananh 7y ago
  it's actually https://microk8s.io https://microk8s.io
- odensc 7y ago
  Interesting, I'll have to look more into that and the differences to k3s. But k3s does support clustering BTW.
castillar76 7y ago
I've had great luck with moving my container stack stuff to Portainer (portainer.io), which will do containers and stacks, but is really user-friendly and low-overhead. Combine it with Ourobouros to download and auto-deploy the latest versions of containers and it's really low-touch.
LockAndLol 7y ago
Thank you very much. I was really not looking forward to running docker in a VM. It seems too much like a case of inception. > Bro, I heard you like virtualization, so we use virtualization inside virtualization to virtualize while we virtualize! Hard pass. I hope this can be a nice alternative to managing docker-compose.

by odensc 7y ago

nullwarp 7y ago

Amen to that, after avoiding kubernetes at home for so long (run a quite a lot of clusters at work in production and while not a nightmare, it is a lot of work) - I've now moved most of my self-hosted stuff to k3s. It's been a joy to work with. We're even looking at starting to migrate most of our edge deployments to k3s as well. Really really awesome piece of work by Rancher.

devit 7y ago
What is the advantage compared to the traditional method of getting a single Linux system or VM, installing the needed packages via apt/yum, rsyncing over your code (if any) and installing systemd units for anything that needs to run all the time or scheduled? Are Helm charts easier to use or more prevalent than distribution packages?

ukd1 7y ago

Similar, and probably slightly easier from my experience, plus supports things like clustering and easily managing service, is microk8s[1] from canonical. [1]: https://microk8s.org https://microk8s.org

tuananh 7y ago
it's actually https://microk8s.io https://microk8s.io
odensc 7y ago
Interesting, I'll have to look more into that and the differences to k3s. But k3s does support clustering BTW.

castillar76 7y ago

I've had great luck with moving my container stack stuff to Portainer (portainer.io), which will do containers and stacks, but is really user-friendly and low-overhead. Combine it with Ourobouros to download and auto-deploy the latest versions of containers and it's really low-touch.

LockAndLol 7y ago

Thank you very much. I was really not looking forward to running docker in a VM. It seems too much like a case of inception. > Bro, I heard you like virtualization, so we use virtualization inside virtualization to virtualize while we virtualize! Hard pass. I hope this can be a nice alternative to managing docker-compose.