Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My self-hosting infrastructure, fully automated

github.com

Post reply on HN
Print view View original

121–130 of 228 posts

Re: My self-hosting infrastructure, fully automated

#121

Post by moontear »

nullwarp wrote: post #87
candiddevmike wrote: post #44

I enjoy reading about homelabs that aren't using kubernetes or some other scheduler and how they're doing it/what the full stack looks like. This is just another "how I installed kubernetes" thing only without any real scale behind it. There are other ways to deploy and run things, and it takes people toying around with alternatives for something unique to spring up.

I've used everything under the sun and for homelab use IMO nothing beats using docker-compose and salt. 1. Unless you have crazy dynamic scaling needs, there's literally no point in using k8s or nomad 2. Unless you want RBAC and fine tuned ACL, theres literally no point in using k8s or Nomad I hate this idea that you need a Ceph cluster and a 3 node HA cluster to have a home lab. Not saying don't do it because you wa…

I also run everything with docker stack(s) currently. Not using salt and haven’t heard of it. Why would I want salt and not ansible or something similar?

Re: My self-hosting infrastructure, fully automated

#122

Post by Datagenerator »

khuedoan wrote: post #50
mcescalante wrote: post #21

Earlier quoted context omitted.

I just stumbled on a self hosted project similar to tailscale: https://github.com/gravitl/netmaker . There is also https://github.com/juanfont/headscale which is an open sourced implementation of the Tailscale coordination server. Tailscale "just works" and makes things incredibly easy for personal use, but it's awesome that there are also similar self-hosted options out there

(Repo owner here) I'm planning to build my own router with OpenWRT and install Wireguard on it, however due to the chip shortage I can't get the hardware for a reasonable price yet. Netmaker looks amazing, I need to play with it.

For small use cases at home you might want to try GL.iNet GL-MT300N-V2 ( generally available within days ). Or virtual for free, ymmv

Re: My self-hosting infrastructure, fully automated

#123

Post by rambambram »

midasuni wrote: post #112
kstenerud wrote: post #107

Earlier quoted context omitted.

Yes, but after the initial monoliths of mainframes, we had a golden era of operating systems, where all of the plumbing and infrastructure to run your applications was maintained by someone else (Microsoft, Apple, Commodore, Atari, SGI, Sun, Palm, Redhat, etc). Now we've come full circle back to the bad old days where you need an entire team of dedicated people and arcane knowledge just to run your application softwa…

Apt install your lamp stack Deploy your files Cronjob to apt upgrade every night Why does that need a full team? Or more than 10 minutes every few years?

I want to visibly second this (with a comment, not only an upvote). I dubbed the LAMP stack the CHAMP stack for some time now (CH standing for CSS and HTML).

Re: My self-hosting infrastructure, fully automated

#125

Post by thejosh »

nullwarp wrote: post #87
candiddevmike wrote: post #44

I enjoy reading about homelabs that aren't using kubernetes or some other scheduler and how they're doing it/what the full stack looks like. This is just another "how I installed kubernetes" thing only without any real scale behind it. There are other ways to deploy and run things, and it takes people toying around with alternatives for something unique to spring up.

I've used everything under the sun and for homelab use IMO nothing beats using docker-compose and salt. 1. Unless you have crazy dynamic scaling needs, there's literally no point in using k8s or nomad 2. Unless you want RBAC and fine tuned ACL, theres literally no point in using k8s or Nomad I hate this idea that you need a Ceph cluster and a 3 node HA cluster to have a home lab. Not saying don't do it because you wa…

I really like nomad for a single node homelab, it's super easy to maintain and deploy stuff.

Re: My self-hosting infrastructure, fully automated

#127

Post by nyellin »

To everyone saying that Kubernetes is unnecessary, try implementing autoscaling, service discovery, secrets management, and autohealing in a vendor independent way without it.

Of course none of that is necessary for a self hosted home lab, but neither is gitops.

This is a very nice example of how to set stuff up properly.

OP, I would love to see Robusta (https://robusta.dev) as part of this too. It's definitely in line with your vision of automating everything, as it let's you automate the response to alerts and other events in your cluster. (Disclaimer: I'm one of the maintainers)

Re: My self-hosting infrastructure, fully automated

#129

Post by 867-5309 »

midasuni wrote: post #112
kstenerud wrote: post #107

Earlier quoted context omitted.

Yes, but after the initial monoliths of mainframes, we had a golden era of operating systems, where all of the plumbing and infrastructure to run your applications was maintained by someone else (Microsoft, Apple, Commodore, Atari, SGI, Sun, Palm, Redhat, etc). Now we've come full circle back to the bad old days where you need an entire team of dedicated people and arcane knowledge just to run your application softwa…

Apt install your lamp stack Deploy your files Cronjob to apt upgrade every night Why does that need a full team? Or more than 10 minutes every few years?

one does not simply "deploy"

Re: My self-hosting infrastructure, fully automated

#130

Post by xupybd »

midasuni wrote: post #112
kstenerud wrote: post #107

Earlier quoted context omitted.

Yes, but after the initial monoliths of mainframes, we had a golden era of operating systems, where all of the plumbing and infrastructure to run your applications was maintained by someone else (Microsoft, Apple, Commodore, Atari, SGI, Sun, Palm, Redhat, etc). Now we've come full circle back to the bad old days where you need an entire team of dedicated people and arcane knowledge just to run your application softwa…

Apt install your lamp stack Deploy your files Cronjob to apt upgrade every night Why does that need a full team? Or more than 10 minutes every few years?

Okay but what happens when you have a breaking change from one of your updates?
Post reply on HN