homelab
home-ops
homelab | home-ops | |
---|---|---|
4 | 52 | |
23 | 1,764 | |
- | - | |
9.9 | 10.0 | |
6 days ago | 2 days ago | |
YAML | Shell | |
MIT License | Do What The F*ck You Want To Public License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
homelab
-
Home Lab Guide
k8s is a lot easier for homelabs than it used to be, and imo it's quicker than nix for building a declarative homelab. templates like this one can deploy a cluster in a few hours: https://github.com/onedr0p/cluster-template
here's my home assistant deployment as a single file: https://github.com/pl4nty/homelab/blob/main/kubernetes/clust...
I deliberately nuked my onprem cluster a few weeks ago, and was fully restored within 2 hours (including host OS reinstalls). and most of that was waiting for backup restores over my slow internet connection
-
What kubernetes platforms do you use in your production environment?
Can't talk about work, but my homelab is Azure and Oracle managed k8s (AKS/OKE), with onprem Talos soon (Turing Pi 2). My Flux monorepo has the details. OKE performs noticably worse (update cycle, features, control plane performance), but it provides 4 ARM cores and 24GB RAM free so I can't complain
-
What was a tech or feature your dismissed as unnecessary initially, but turned out to be wrong?
Here's my cluster's IaC if you want to take a look, it's pretty optimised for web services though. It's all Linux too - I've attempted Windows containers but Windows apps don't often handle state well
-
Best small cluster provider for $50/mo?
It's been a good way to test ARM before I build a Pi cluster. My manifests and container builder are public if you want to take a look. I use a base layer for networking and observability, so it's easy to move stateless workloads, but I still need to sort out volume replication/backups
home-ops
-
Ditching PaaS: Why I Went Back to Self-Hosting
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.
-
Homelab setup for Kubernetes training
Going thru this repo https://github.com/onedr0p/home-ops
- Selfhosted k8s for home server?
-
My recently deployed media apps in ArgoCD, migrating from Terraform.
Take a look at my open source GitOps repo managed by Flux here: https://github.com/onedr0p/home-ops
- How do You manage Your docker containers configuration?
-
Self Hosted SaaS Alternatives
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.
- Deploying apache guacamole on k8s
-
My completely automated Homelab featuring Kubernetes
My Kubernetes cluster, deployments, infrastructure provisioning is all available over here on Github.
-
Container Updating Strategies
For example: https://github.com/onedr0p/home-ops/pull/4528
-
Simple self-hosted S3-compatible
I'm running minio in my cluster with NFS backend just fine. You can see my deployment of it here.
What are some alternatives?
containers - Container images for various applications
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
k8s-gitops - Kubernetes cluster powered by GitOps with FluxCD- Unified source of truth, automated workflows, declarative infrastructure, and cutting-edge DevOps practices.
cluster-template - A template for deploying a Kubernetes cluster with k3s or Talos
k8s-gitops - GitOps principles to define kubernetes cluster state via code
longhorn - Cloud-Native distributed storage built on and for Kubernetes
shell - Pop!_OS Shell
gocast - GoCast is a tool for controlled BGP route announcements from a host
talos - Talos Linux is a modern Linux distribution built for Kubernetes.
motioneye - A web frontend for the motion daemon.
charts - Community Helm Chart Repository
renovate-helm-releases - Creates Renovate annotations in Flux2 Helm Releases