5 ms·
For what it's worth, I built one like this on an old Linux laptop. I then moved my home lighting controller onto it as a test. Some months later my house lights
by wpietri 7y ago
For what it's worth, I built one like this on an old Linux laptop. I then moved my home lighting controller onto it as a test. Some months later my house lights stopped working, and I had to spend a few hours applying snippets semi-randomly from Stack Overflow. It could be the problem was due to expired Kubernetes certificates, or it could be something else.
Either way, my conclusion was that Kubernetes is really meant for more scale and attention than I like to give my home infrastructure, so although I enjoyed the experiment, I would encourage people not to run important services on something like this.
- hnarn 7y agoI have a strong feeling that the added complexity of Kubernetes does not give most use cases a net payoff for hobbyists. A lot of the quirks and monkey wrenching with both Docker and Kubernetes seems to be like problems that in many cases were solved in traditional _NIX systems decades ago. I'm sure there are benefits of throwing some of that architecture out for some scenarios but people shouldn't treat it as a new paradigm by default.
- karatestomp 7y agoDocker's been great for hobbyist stuff for me. But I don't really use anything fancy on it, just map some folders for storage I want to survive rebuilds[1] and forward necessary ports to the host machine's interfaces. I don't rely on swarm or any of that. I mostly use it to avoid having to worry about distro-specific crap, since I no longer care to (re-)learn any of that. I don't even use docker-compose since almost none of my personal services depend on one another, just simple shell scripts that all look pretty similar. [1] In some ways this is easier than running traditional daemons, as storage locations for dockerized services tend to be well-documented, prominently, all in one place, and don't change from, say, one package manager to another. You can very easily get all your dockerized services storing their important stuff under one isolated tree, and back up the whole thing. That plus your run scripts are all you need to restore, no matter which host platform you use. [EDIT] in fact, getting Samba set up for my super simple and surely common use case of "I want these folders shared read-only for everyone, and these others writable for this one user" was much easier with Docker than it's been since back when I used Gentoo. The fancier distros all seem to make it a big pain in the ass to do anything other than sharing user directories through the GUI, and change Samba configs between seemingly every major release, and they're always a mess. With the Dockerized version it was one short and sweet arcane magical line per directory I wanted to share, so no clearer, but very short and worked on the first try.
- lonelappde 7y agoIt's not helpful to say some unspecified thing is better than a concrete thing people use. What Unix tools are an alternative for Docker? I install an app, I download a VM image, and I have a dynamically sized VM with a nice simple UI to control it. VirtalBox is fine too but more heavyweight for multiple VMs at once, and Docker is where the community and premade VMs images are. Works on any platform. k8s is probably overkill if you aren't prototyping a production cluster.
- wpietri 7y agoPackaging an app in Docker is work up front and then ongoing overhead to manage. If something I write is only going to ever run on one server, it may be easier for me just to install it on the base system, not in a container.
- rumanator 7y ago> I have a strong feeling that the added complexity of Kubernetes does not give most use cases a net payoff for hobbyists. Kubernetes is a tool to setup and manage computer clusters comprised of COTS hardware, and also manage how processes are deployed and ran on it. That's not exactly your typical hobbyist's scale.
- odensc 7y agoFYI, 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 agoAmen 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 agoWhat 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 agoSimilar, 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
- spalas 7y agoInteresting, and I agree that this is not a suitable location for running anything important! I mostly use it for random experimentation/learning and like not having to think about starting up/shutting down Minikube on my main laptop!