home-cluster

My home Kubernetes (k3s) cluster managed by GitOps (Flux) (by onedr0p)

Stats

Basic home-cluster repo stats
12
80
0.0
4 days ago

onedr0p/home-cluster is an open source project licensed under The Unlicense which is not an OSI approved license.

Home-cluster Alternatives

Similar projects and alternatives to home-cluster

  • GitHub repo template-cluster-k3s

    Template for creating a k3s cluster with k3sup backed by flux and sops

  • GitHub repo nomad-driver-containerd

    Nomad task driver for launching containers using containerd.

  • GitHub repo k0s

    k0s - Zero Friction Kubernetes

  • GitHub repo hcl

    HCL is the HashiCorp configuration language.

  • GitHub repo sealed-secrets

    A Kubernetes controller and tool for one-way encrypted Secrets

  • GitHub repo piku

    The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.

  • GitHub repo awesome-gitops

    A curated list for awesome GitOps resources

  • GitHub repo actions-runner-controller

    Kubernetes controller for GitHub Actions self-hosted runnners

  • GitHub repo charts

    Helm charts for applications you run at home (by k8s-at-home)

  • GitHub repo pirsch

    Pirsch is a drop-in, server-side, no-cookie, and privacy-focused analytics solution for Go.

  • GitHub repo awesome-home-kubernetes

    Awesome projects involving running Kubernetes at home

  • GitHub repo tools

    OPNsense release engineering toolkit (by opnsense)

  • GitHub repo Fly CDN

    A set of useful libraries for Edge Apps. Run locally, write tests, and integrate it into your deployment process. Move fast and maybe don't break things? Because, gosh darnit, you're an adult. (by superfly)

  • GitHub repo vaku

    Vaku extends the Vault API & CLI

  • GitHub repo gocast

    GoCast is a tool for controlled BGP route announcements from a host

  • GitHub repo infrastructure

    (WIP) Terraform configuration of the ironpeak infrastructure. (by ironpeakservices)

  • GitHub repo nerdctl

    Moved to https://github.com/containerd/nerdctl

  • GitHub repo k3s-cluster

    K3S cluster installation and configuration (by glenbot)

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better home-cluster alternative or higher similarity.

Posts

Posts where home-cluster has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-05-05.
  • BGP Setup for MetalLB load balancer advertising
    Unfortunately the opnsense kernel doesn't support multipath routing which means if your scale a deployment to greater than 1 replica it not be load balanced between the pods. See my explanation here as well.
  • 8 Node NUC K8S Cluster
    reddit.com/r/homelab | 2021-05-03
    You can see it in use with my GitOps repo
  • Template for deploying k3s backed by Flux and more goodies
    This is great, I remember stumbling across your own repo with all this and building my own.
    reddit.com/r/homelab | 2021-04-17
  • How to host a set website on a raspberry k3s cluster with nginx-ingress, metallb and Cert-Manager ?
    If you wish you can take a look at my gitops repo where I more deployments and config.
  • The Decline of Heroku
    news.ycombinator.com | 2021-04-12
    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 so 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

  • Running Nomad for a Home Server
    news.ycombinator.com | 2021-02-15
    A whole lot of "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.

    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. 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 turn it into a running, healing, backing-up replicated postgres cluster. Take a SQS object and with ACK turn it into a real SQS.

    Kubernetes & cloud native in 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

  • My home kubernetes cluster managed by Flux2 and RenovateBot
    I use it to monitor Flux HelmReleases and Kubernetes manifest to watch and open PRs when it finds a helm chart or container image upgrades. Feel free to poke around at my config.
    Velero exports metrics so you can set up rules for alert-manager if you're into that kind of thing, botkube can also report out on velero too.
  • Show HN: My Home Kubernetes Cluster Managed by Flux2 and Renovatebot
    news.ycombinator.com | 2021-01-23
  • RClone sync in Docker: just do a custom dockerfile?
    reddit.com/r/rclone | 2021-01-19