The name seems to imply this project is 3x smaller than K3S[0], does it use less memory, CPU? If this is all about removing external dependencies, I don't think is worth creating an entire new project to avoid installing something like `socat`. [0] https://k3s.io/
K0s – Zero Friction Kubernetes
11–20 of 78 posts
Re: K0s – Zero Friction Kubernetes
#12If that is too much, is k8s even relevant to your case?
Say your workload is so small and so simple that having a minimum of 2 servers isn't what you want, then again, is k8s even relevant for your case?
Or perhaps the better question: who is this for?
Re: K0s – Zero Friction Kubernetes
#13Earlier quoted context omitted.
K3s is definitely more lightweight than K8s, but it still requires non-negligible resources. Compared to just a Docker engine, it takes more memory and CPU, which can be noticeable on smaller servers, Raspberry Pi, and such.
Ah, I see, thank you. Sounds like just manually starting docker-compose stuff will be preferable right now.
Re: K0s – Zero Friction Kubernetes
#14Earlier quoted context omitted.
Ah, I see, thank you. Sounds like just manually starting docker-compose stuff will be preferable right now.
I'd make systemd unit files around the docker-compose deployments. Upload everything with something like Ansible. If you want to go perfect go for NixOS instead, but that might be controversial.
Re: K0s – Zero Friction Kubernetes
#15Re: K0s – Zero Friction Kubernetes
#16So question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/
Re: K0s – Zero Friction Kubernetes
#17Has anyone used K3s or this? Are they a good alternative to Dokku? I'm looking for something to either deploy on a server to host all my sideprojects (though Dokku has been basically perfect so far), or on my home server for various things like Gitea, Nextcloud and random scripts. Is K3s/K0s a good idea for either of those?
I have tried k3s and microk8s. Recently setup ArgoCD, connected to our GitLab instance. Tried both Traefik and Nginx Ingress controllers. And so on. And dokku is better if you want a PaaS. There are probably dokku/heroku/deis-like things that run on kubernetes, but so far I haven't found 'it'. Of course you can just run dokku on any k8s distribution. You can even use k8s as a backend for dokku instead of docker - htt…
Re: K0s – Zero Friction Kubernetes
#18So question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/
'k8s' is a numeronym: the '8' denotes eight omitted letters ('ubernete').
https://en.m.wikipedia.org/wiki/Special:MobileDiff/943694377
Re: K0s – Zero Friction Kubernetes
#19Earlier quoted context omitted.
I'd make systemd unit files around the docker-compose deployments. Upload everything with something like Ansible. If you want to go perfect go for NixOS instead, but that might be controversial.
Doesn't Compose take care of that with "restart: always"? Though that probably doesn't work on reboot...
Re: K0s – Zero Friction Kubernetes
#20Earlier quoted context omitted.
I'd make systemd unit files around the docker-compose deployments. Upload everything with something like Ansible. If you want to go perfect go for NixOS instead, but that might be controversial.
Doesn't Compose take care of that with "restart: always"? Though that probably doesn't work on reboot...
https://docs.docker.com/config/containers/start-containers-a...