HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
onedr0p
home-ops
YAML2021–2025
onedr0p / home-ops

home-ops

Wife approved HomeOps driven by Kubernetes and GitOps using Flux

3Distinct people
12Mentions
2Explicit recommenders
2.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Wife approved HomeOps driven by Kubernetes and GitOps using Flux

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

This is incredibly popular a take, and this anti-k8s is rapidly upvoted almost every time. The systemd hate has cooled a bit, but it too functions as a sizable attractor for…

jauntywundrkind used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 11:20:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2021-01-24 00:13:40 UTC to 2025-06-30 16:16:24 UTC.

012342021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC413
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

What Hacker News says

4 sources
Great list. One thing I want to reinforce is that the leading edge engineers of the world are only just starting to surface wide-scale, acceptable, happy practices for running systems/software. It's only in the past couple years that "build a cluster of raspberry pi's" has become a "legible"/comprehensible pitch, something that makes a light bulb go off over people's heads. A couple years ago we wouldn't really have known what to think, what that would be good for. But now we have the shared language, the operational tools (& culture) to imagine clusters of computing resources coming together, reinforcing & helping one another, providing reliability & stable known operating environments for a vast variety of "easy" to launch workloads. To the point that a hobbyist can bring up a pi cluster mini-data-center in less than a weekend. That's d
Read the rest
raw dropping amazing, & a colossal demonstration of how much mastery we've achieved over such a wide wide set of concerns. 5 years ago we didn't even have the shared language to express the goal/desire, the cloud was abstract, but now it's real & something we can do for $120 and a couple hours. And we'll only get better. We're only really just getting started with this inertia, only just started bringing a lot of big ideas into the commons. While the primary drivers are big & medium entities doing ops, this is a huge foothold for the home, for the hobbyist to get going with, to make running software simple but not too simple, to have a platform that scales from very low & easy to very big & fancy. There's a lot of epic & amazing home-cloud stuff going on, & this is all so new, & very technical, but over time I expect a lot of paths to be paved, a lot of lessons learned, and the amazing ultra-leading-edge works like onedr0p's homecloud[1] to spring into bloom & to seed new efforts. Having a rich, high-potential ecosystem that computing & the computing community can build atop of & get good & get more elegant with is a precondition for any other part of computing succeeding. Without good ops, personal computing can go nowhere, and we are so so so much better gathered & doing so much better than we were even half a decade ago. Once our own computing becomes possible, the spread of p2p & distributed systems might start. Even that doesn't seem ultra-necessary to me. I believe the mediums we have are enormously powerful, enormously flexible, and incredibly distributed if put to use for those ends. Specs like ActivityPub and ActivityStreams can remake how almost all software works, can provide the fabric of connectivity that makes connected networked systems so compelling, so interesting to participate in, without the top-down-control, with self-determinism & agency & genuine ownership of data. That we can have amazing new online vantage points for these wide & diverse feeds of information when we harken to protocols & feeds. Still missing right now, mobile/low power systems are still trapped in the old world: the most important device we own, our phones, can not participate in the new dawning better-ops cross-system-ops galaxy we are breathing life into. Unlocking mobile from the confines of narrow consumerdom is a long battle, and I mostly hope the overwhelming brilliance of self-hosting Linux makes Linux on the phone too compelling to allow these consumer, [1] https://github.com/onedr0p/home-cluster
In My love-hate affair with technology
huge fan of k8s. drop what you're doing & use a cross-system object-storage/"apiserver" & control-loops to automate everything; embrace desired state management & thank me latter. but, Heroku &al have a lot of value left. there's just not that many folk trying to tame deploys on k8s via gitops. flux2 is the rage, it's all over the alpha geek's efforts[1], but it's usually used by someone carefully authoring a fairly complex Helm file, then building out a significant Flux2 HelmRelease object (ex: [2]). there's a bunch of other tools[3], & i'm frankly not familiar enough. but this idea of having a bunch of source that can deploy itself, simply, is still extremely rare even among the alpha-geek #gitops types. i'm sure some of these tools better match the simplicity of the Heroku model, corresponding branches to environments, which makes so s
Read the rest
o much sense, but so far i feel like such attempts are still basically unknown. heroku's really simmered it down to something that made extremely natural sense. huge props to that. too too much of this effort had to go into creating buildpacks & supporting language environments very very carefully very actively, that ability to stealth-containerize an app & not even notice is so much of the special sauce that makes this a hard, hard & eternal problem (because langauges/envs keep changing). there's still a lot of ease of use to Heroku that's potentially will be underrated and/or lost by the oncoming generations. i have high respect for how operateable Heroku is. [1] https://github.com/k8s-at-home/awesome-home-kubernetes [2] https://github.com/onedr0p/home-cluster/blob/main/cluster/ap... [3] https://github.com/weaveworks/awesome-gitops#tools
In The Decline of Heroku
A whole lot of anti- Kubernetes "you most likely don't need them and the increase in complexity makes it a pain to maintain" and "Kubernetes is exceedingly complex" in this thread & somewhat in this article. I agree that you probably don't need Kubernetes, and perhaps yeah it could be considered complex. But I think it's the right fit for most developers/doers & over time most operators too. Kubernetes is not Kubernetes. Kubernetes is some base machinery, yes, but it's also a pattern, for writing controllers/operators that take Kubernetes Objects and turn them into things. Take a Postgres object and let postgres-operator turn it into a running, healing, backing-up replicated postgres cluster. Take a SQS object and let ACK turn it into a real SQS. Take a PersistentVolume and with Rook turn it into a Ceph store. Kubernetes & cloud native in
Read the rest
general proposes that you should have working models for the state of your world. In addition to the out-of-the-box machinery you get for running containers (deployment-sets), exposing them (services), &c, you get this pattern. You get other folks building operators/controllers that implement this pattern[1]. You get a consistent, powerful, extensible way of building. Nothing else comes close. There's nothing remotely as interesting in the field right now. The Cult of Easy is loud & bitterly angry about Kubernetes, hates it's "complexity", but what is actually complex is having a dozen different operational environments for different tools & systems. What is actually complex is operating systems yourself, rather than having operators to maintain systems. Kubernetes has some initial costs, it can feel daunting, but it is radically simpler in the long run because _it has a paradigm,_ an all inclusive paradigm that all systems can fit into, and the autonomic behaviors this paradigm supports radically transfer operational complexity from human to computer, across that broad/all-inclusive range of systems. There's a lot of easier this/harder that. No one tries to pitch Nomad or anything else as better, as deeper, as being more consistent, having a stronger core. Every article you hear on an alternative to Kubernetes is 98% "this was easier". I think those people, largely, miss the long game, the long view. A system that can adapt, that operationally can serve bigger & bigger scopes, ought to pay dividends to you as years go by. Kubernetes may take you longer to get going. But it is time enormously well spent, that will increase your capability & mastery of the world, & bring you together with others building radically great systems whether at home[2][3] or afar. It will be not just a way of running infrastructure, but help you re-think how you develop, and how to expose your own infrastructure & ideas more consistently, more clearly, in the new pattern language of autonomic machines that we have only just begun to build together. I encourage the bold explorers out there, learn Kubernetes, run Kubernetes. And to those of you pitching other things, please, I want you to talk up your big game better, tell me late-game scenarios, tell me how your system & I are going to grow together, advance each other. [1] https://kubernetes.io/docs/concepts/architecture/controller/... [2] https://github.com/onedr0p/home-cluster [3] https://github.com/k8s-at-home/awesome-home-kubernetes
In Running Nomad for a Home Server

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.