Set up a self-hosted home server cluster on Raspberry Pi hardware running multiple applications through Kubernetes.
Learn how to structure a small GitOps-managed Kubernetes environment with clear separation between platform, shared services, and applications.
Use the manifests as a pattern library for how to organize Kubernetes apps into namespaces, network policies, storage, and monitoring bundles.
| abhi1693/homelab | misterio77/hackathon-mgc-factorio-terraform | faizanfirdousi/alchemyst-assign | |
|---|---|---|---|
| Stars | 2 | 2 | 1 |
| Language | HCL | HCL | HCL |
| Last pushed | — | 2025-10-13 | — |
| Maintenance | — | Quiet | — |
| Setup difficulty | hard | hard | hard |
| Complexity | 5/5 | 4/5 | 4/5 |
| Audience | ops devops | ops devops | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires multiple ARM64 nodes (Raspberry Pi), a home router supporting BGP, domain ownership, and significant Kubernetes and networking knowledge to operate.
This repository documents and operates a home server cluster built on Raspberry Pi computers running ARM64 chips. The cluster uses Kubernetes (specifically a lightweight distribution called K3s) to run self-hosted applications including media management, home automation, databases, monitoring, and developer workspaces. Everything is managed through code: Ansible handles the initial setup of each node and the cluster bootstrap, and Rancher Fleet handles ongoing application deployment by reading Git as the source of truth. The design covers the full path from bare hardware to running applications. That includes how nodes are prepared and joined into a cluster, how networking is set up with Cilium (which handles traffic routing, load balancing, and network policies), how storage is provided through Longhorn, how shared services like PostgreSQL and a Redis-compatible cache are made available to applications, and how secrets are managed with SOPS. Applications are organized into separate Rancher projects (applications, media, home automation, databases, system services, and developer tools) so that a problem in one area does not cascade into others. The repository explicitly describes itself as a reference implementation rather than a one-command installer. It shows how a small Kubernetes environment can be layered and structured, but it does not pretend to handle site-specific details like your home network configuration, domain names, or hardware inventory. The README is exceptionally detailed, covering topology diagrams, traffic models, storage design, and the reasoning behind specific technology choices like why Cilium was selected over simpler networking options. One notable inclusion is Coder, a tool for running cloud-style developer workspaces inside the homelab, with HCL templates for defining workspace environments. The README is lengthy and the full content was not provided. The license is not mentioned in the available portion of the README.
A fully documented Raspberry Pi Kubernetes homelab that manages everything through code: Ansible bootstraps the cluster, Rancher Fleet deploys apps via GitOps, and shared services support media, home automation, and developer workspaces.
Mainly HCL. The stack also includes HCL, Ansible, Kubernetes.
License not stated in the README.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.