Home-Ops
My Home Operations repository
... managed by Flux, Renovate and GitHub Actions 
Inspiration
This is heavily inspired by the wonderful work done by the k8s-at-home community.
Peep their discord!
The structure of this repo stands on the shoulder of giants:
Hardware
| Device | Count | OS Disk Size | Data Disk Size | NIC | Operating System | Purpose |
|---|---|---|---|---|---|---|
| Lenovo Thinkcentre m720q | 2 | 500GB NVME | Fedora | Kubernetes Control Plane | ||
| Lenovo Thinkcentre m920q | 1 | 500GB NVME | Fedora | Kubernetes Control Plane | ||
| Dell Optiplex 3070 SFF (9th-gen Intel i5) | 3 | 250GB SSD | 1x 1TB SSD; 1x 1TB NVME | Mellanox ConnectX-3 10G | Fedora | Kubernetes Agent |
| Custom NAS (Fractal 304) | 1 | Mellanox ConnectX-3 10G | Unraid | NAS | ||
| Lenovo Thinkcentre m720q | 1 | VyOS | Router | |||
| Brocade ICX6450 | 1 | Switch | ||||
| TP-Link EAP650 | 1 | Wifi AP | ||||
| Unifi Flex-Mini | 2 | Switch (per room) | ||||
| RPI 4B w/ Hifiberry DAC2 Pro | 1 | Volumio |
Kubernetes
Installation
A private repo with my ansible playbooks provision k3s atop baremetal Fedora 37-Server installs.
Someday I'll switch over to the flux-cluster-template - right now what I use is something of a messy bastardization of the techno-tim/k3s-ansible playbooks.
Storage
The cluster is mostly hyper-converged; block-storage is provisioned through Longhorn on dedicated SSD and NVME drives per worker node.
A separate NAS runs Unraid for NFS, but that is solely for media storage.
Layout
This Git repository contains the following directories under kubernetes.
📁 kubernetes # Kubernetes cluster defined as code
├─📁 bootstrap # Flux installation
├─📁 flux # Main Flux configuration of repository
└─📁 apps # Apps deployed into my cluster grouped by namespace
Flux is continually syncing the state of this repository to the cluster and applying any changes found in the kustomizations within.
No kubectl apply or helm install|upgrade for me. The flux controllers on the cluster
do all the work. 