Why would you do this for simple home apps? k8s is complete overkill. At home, there is little reason to drag in all that complexity to host a blog or whatever. Kubernetes drags in a tremendous amount of complexity, background knowledge, and strange constraints, even on small installations. I really do not see its benefit for small apps and projects. Are you hosting your blog? You don't need k8s. Are you running a sm…
Learning?
Domesticating Kubernetes
71–80 of 100 posts
Re: Domesticating Kubernetes
#72question: if not k8s, what everyone has been using to orchestrate containers at home? Ideally, I just want something easy to setup, low maintenance cost and easy to backup and restore if sth went wrong. i've been using k8s at work for over 4 years but for home usage, it's just too much.
Re: Domesticating Kubernetes
#73you 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/ here's a live walkthrough - https://www.youtube.com/watch?v=DjpVtNjiXSU
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.
Last I checked, K3s is a fully certified distro of k8s.
Re: Domesticating Kubernetes
#74you 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/ here's a live walkthrough - https://www.youtube.com/watch?v=DjpVtNjiXSU
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?
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.
Re: Domesticating Kubernetes
#75Earlier quoted context omitted.
I do not blame you. I try to avoid it as long as it is possible. The amount of time, energy and effort wasted on this is just insane.
Hosted k8s has changed my life. Let me focus on my business and not my infra.
Re: Domesticating Kubernetes
#76Re: Domesticating Kubernetes
#77I've given up running my own k8s at home a couple of times. It does seem to be getting easier, but then upgrading and maintaining breaks me again. + the other stuff like running your own container registry. Then with new centos podman breaks everything that worked OK in docker. I hate this stuff, so many problems its worth ignoring the whole stack.
what do you end up using instead of k8s?
Re: Domesticating Kubernetes
#78Earlier quoted context omitted.
what do you end up using instead of k8s?
I mostly use docker compose. Perfect fit for tinkering but not over complicated and huge ram eater. Also:k3s might be an option.
If you run your home server on a separate box, like a RaspPi or NUC, docker-machine via SSH can make provisioning and updating a tad easier.
Re: Domesticating Kubernetes
#79Earlier quoted context omitted.
Hosted k8s has changed my life. Let me focus on my business and not my infra.
Have you had any serious yet? If you are on the happy path does not really matter what you use.
Re: Domesticating Kubernetes
#80Earlier quoted context omitted.
Hosted k8s has changed my life. Let me focus on my business and not my infra.
expensive though?
If I want to shave pennies, I have many places to shave before the very thing that is the heart of my business.