home-ops VS homelab

These are great operational wins. Agreed very much that having autonomic (can fix itself) systems at your back is a massive game changer. De-crustifies the act of running things.

The other win is that there's a substantial cultural base to this way to go. Folks have been doing selfhosting for ages, but everyone has their own boutique setup some their way. A couple tools and techniques could be shared, but mostly everyone took blank slate configs & built their own system up, & added their own monitoring & operational scripts.

https://github.com/onedr0p/home-ops is a set of helm scripts and other tools that is widely widely used, and there's a lot more like it. It's a huge build out, using convention and a common platform to enable portable knowledge & sharing.

Self hosting did not have intellectual scale out at it's back, before Kubernetes came along. Docker and ansible and others have been around, but theres never been remotely the success there has been today in empowering users to setup & run complex services.

We really have clawed out of the server-hugging jungle &started building some villages. It's wonderful to see.

Going thru this repo https://github.com/onedr0p/home-ops

Take a look at my open source GitOps repo managed by Flux here: https://github.com/onedr0p/home-ops

Im fully onboard with the geneneral idea as a target.

Right now it's for early early adopters. Hosting stuff is still a painm But we are getting better at hosting stuff, finding stable patterns, paving the path. Hint, it's not doing less, it's not simpler options: it's adopting & making our own industrial scale tooling. https://github.com/onedr0p/home-ops is a great early & still strong demonstration; the up front cost od learning is high, but there's the biggest ecosystem of support you can imagine, and once you recognize the patterns, you can get into flow states, make stuff happen, with extreme leverage far beyond where humanity has ever been. Building the empowered individual is happening, and we're using stable good patterns that will mean the individual isnt so off on their own doing ops- they'll have a lot more accrued human experiene at their back, their running of services isnt as simple to understand from the start but goes much much further, is much more mature & well supported in the long run.

My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.

For example: https://github.com/onedr0p/home-ops/pull/4528

I'm running minio in my cluster with NFS backend just fine. You can see my deployment of it here.

K3s is great, I use it on all of my personal clusters (here and here). It's lightweight and very easy to manage.

https://github.com/khuedoan/homelab if you haven't come across it yet. To add to your bookmarks.

I have my Kubernetes homelab public on GitHub, everything is automated and defined as code. Hope it will help you get started and see what's possible.

So I 've got inspired by https://github.com/khuedoan/homelab and initially after lurking this sub for a while I came up with a plan to consider some of these solutions: - openmediavault as a VM to use 2x4TB /w ext4 & mergerFS or TrueNAS in RAID1 - I think mergerFS gives more options to increase storage with extra drives later, but I don't plan to hoard lots of data. Also rather opted for tiered cache via SSD to save some power but if such lot of VMs would write this would work? - nextcloud VM to easiely manage files via browser and have mobile app sync for photos with some kind of gallery plugins etc - I think this may be optional if there's other solution as nextcloud seems to not be light. Or something like Seafile would be enough? - kubernetes - k3s/microk8s single VM node or 2 VM nodes - would I need more? and so - can then openmediavault be used as a storage for it like TrueNAS? - Rancher - if used k3s - I quite liked the UI of rancher desktop, more than portainer when I tried with microk8s, but I don't pass on using something else, eg. Lens - Gitea - for hosting code - tekton / teamcity - for running tests and commit build hooks - fluxCD / argoCD - for deploying builds to kubernetes

khuedoan/homelab

Here's my project (running on 4 mini PC) that I'm using for learning and self-hosting https://github.com/khuedoan/homelab, it's fully automated from empty disk to operating services.

You can checkout my repo If you'd like to do the same for your homelab (it's also modular so you can just use the OS installation part)

Here're the links to the Markdown source and the web view.

You can checkout my Kubernetes homelab, it's fully automated from empty disk, very customizable and extensible.

You can view the code here: https://github.com/khuedoan/homelab (the ./metal folder)