Live data from Hacker News

K0s – Zero Friction Kubernetes

github.com

11–20 of 78 posts

Re: K0s – Zero Friction Kubernetes

#11
post #5

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/

k3s recently switched to embedded etcd, so if you want something very lightweight out of the box (yet with HA), try Canonical's microk8s it has dqlite support.

Re: K0s – Zero Friction Kubernetes

#12
I don't understand why people seem to want K8s but then find it 'difficult'. It's really not that complex, and when you add stuff on to it, that is your own choice (just like with k3s and k0s). You essentially end up with a kubelet, apiserver (with etcd) and two or three copy-and-paste YAML files (manifests) to setup a 'full' k8s cluster.

If 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

#13
post #10

Earlier 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.

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

#14
post #13
post #10

Earlier 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.

Doesn't Compose take care of that with "restart: always"? Though that probably doesn't work on reboot...

Re: K0s – Zero Friction Kubernetes

#17
post #8
post #6

Has 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…

dokku is fun to play with but I found it too buggy for use in production.

Re: K0s – Zero Friction Kubernetes

#18
post #15

So question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/

This is such a common question that I was motivated to add it to the Wikipedia page. Unfortunately, someone decided to revert it.

'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

#19
post #14
post #13

Earlier 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...

It does!

Re: K0s – Zero Friction Kubernetes

#20
post #14
post #13

Earlier 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...

"restart: always" and "restart: unless-stopped" both work fine after reboot on my system. (Although Docker recommends managing it using systemd or upstart if you want more granular control).

https://docs.docker.com/config/containers/start-containers-a...

Post reply on HN