This is a repository for my home infrastructure and Kubernetes cluster. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Kubernetes, Flux, Renovate, and GitHub Actions.
This semi hyper-converged cluster operates on Talos Linux, an immutable and ephemeral Linux distribution tailored for Kubernetes, and is deployed on bare-metal MS-A2 workstations. Rook supplies my workloads with persistent block, object, and file storage, while a separate server handles media file storage. The cluster is designed to enable a full teardown without any data loss.
There is a template at onedr0p/cluster-template if you want to follow along with some of the practices I use here.
- actions-runner-controller: Self-hosted Github runners.
- cert-manager: Creates SSL certificates for services in my cluster.
- cilium: eBPF-based networking for my workloads.
- cloudflared: Enables Cloudflare secure access to my routes.
- external-dns: Automatically syncs ingress DNS records to a DNS provider.
- external-secrets: Managed Kubernetes secrets using 1Password Connect.
- multus: Multi-homed pod networking.
- rook: Distributed block storage for peristent storage.
- spegel: Stateless cluster local OCI registry mirror.
- volsync: Backup and recovery of persistent volume claims.
Flux watches my kubernetes folder (see Directories below) and makes the changes to my clusters based on the state of my Git repository.
The way Flux works for me here is it will recursively search the kubernetes/apps folder until it finds the most top level kustomization.yaml per directory and then apply all the resources listed in it. That aforementioned kustomization.yaml will generally only have a namespace resource and one or many Flux kustomizations (ks.yaml). Under the control of those Flux kustomizations there will be a HelmRelease or other resources related to the application which will be applied.
Renovate monitors my entire repository for dependency updates, automatically creating a PR when updates are found. When some PRs are merged Flux applies the changes to my cluster.
This Git repository contains the following directories under kubernetes.
📁 kubernetes # Kubernetes cluster defined as code
├─📁 apps # Apps deployed into my cluster grouped by namespace (see below)
├─📁 components # Re-usable kustomize components
└─📁 flux # Flux system configurationThis is a high-level look how Flux deploys my applications with dependencies. In most cases a HelmRelease will depend on other HelmRelease's, in other cases a Kustomization will depend on other Kustomization's, and in rare situations an app can depend on a HelmRelease and a Kustomization. The example below shows that atuin won't be deployed or upgrade until the rook-ceph-cluster Helm release is installed or in a healthy state.
graph TD
A["📦 Kustomization: rook-ceph"]:::kustom -->|Creates| B["🎯 HelmRelease: rook-ceph"]:::helm
A -->|Creates| C["🎯 HelmRelease: rook-ceph-cluster"]:::helm
C -->|Depends on| B
D["📦 Kustomization: atuin"]:::kustom -->|Creates| E["🎯 HelmRelease: atuin"]:::helm
E -->|Depends on| C
classDef kustom fill:#4CAF50,stroke:#2E7D32,stroke-width:2px,color:#fff,font-weight:bold;
classDef helm fill:#2196F3,stroke:#0D47A1,stroke-width:2px,color:#fff,font-weight:bold;
%% Gradients (Mermaid doesn't support native gradients yet, so we mimic with softer colors)
classDef kustom fill:#43A047;
classDef helm fill:#1976D2;
Click to see a high-level network diagram
graph TD
%% Class Definitions
classDef wan fill:#f87171,stroke:#fff,stroke-width:2px,color:#fff,font-weight:bold;
classDef core fill:#60a5fa,stroke:#fff,stroke-width:2px,color:#fff,font-weight:bold;
classDef agg fill:#34d399,stroke:#fff,stroke-width:2px,color:#fff,font-weight:bold;
classDef switch fill:#a78bfa,stroke:#fff,stroke-width:2px,color:#fff,font-weight:bold;
classDef device fill:#facc15,stroke:#fff,stroke-width:2px,color:#000,font-weight:bold;
classDef vlan fill:#1f2937,stroke:#fff,stroke-width:1px,color:#fff,font-size:12px;
%% Nodes
RCN[🛜 RCN<br>5Gbps WAN]:::wan
UDM[📦 UDM Pro]:::core
AGG[🔗 Aggregation<br>10/25Gb]:::agg
NAS[💾 NAS<br>1 Server]:::device
K8s[☸️ Kubernetes<br>3 Nodes]:::device
SW[🔌 24 Port<br>2.5G PoE]:::switch
DEV[💻 Devices]:::device
WIFI[📶 WiFi Clients]:::device
%% Subgraph for VLANs
subgraph VLANs [LAN +vlan]
direction TB
LOCAL[LOCAL<br>192.168.0.0/24]:::vlan
TRUSTED[TRUSTED*<br>192.168.1.0/24]:::vlan
SERVERS[SERVERS*<br>192.168.10.0/24]:::vlan
SERVICES[SERVICES*<br>192.168.20.0/24]:::vlan
IOT[IOT*<br>192.168.30.0/24]:::vlan
GUEST[GUEST*<br>192.168.40.0/24]:::vlan
end
style VLANs fill:#111,stroke:#fff,stroke-width:2px,rx:0,ry:0,padding:20px;
%% Links
RCN -.->|WAN| UDM
UDM --> AGG
AGG -- 10G LACP --- NAS
AGG -- 10G LACP --- K8s
AGG -- 10G LACP --- SW
SW --> DEV
SW --> WIFI
%% Style the bonded links thicker
linkStyle 2 stroke-width:4px,stroke:34d399;
linkStyle 3 stroke-width:4px,stroke:34d399;
linkStyle 4 stroke-width:4px,stroke:34d399;
In my cluster there are two instances of ExternalDNS running. One for syncing private DNS records to my UDM Pro Max using ExternalDNS webhook provider for UniFi, while another instance syncs public DNS to Cloudflare. This setup is managed by creating routes with two specific gatways: internal for private DNS and external for public DNS. The external-dns instances then syncs the DNS records to their respective platforms accordingly.
Click to see my rack
| Device | Count | OS Disk Size | Data Disk Size | Ram | Operating System | Purpose |
|---|---|---|---|---|---|---|
| MS-A2 (AMD Ryzen™ 9 9955HX) | 3 | 1.92TB M.2 | 3.84TB U.2 + 1.92TB M.2 | 96GB | Talos | Kubernetes |
| Synology NAS RS1221+ | 1 | - | 8x22TB HDD | 32GB | DSM 7 | NFS |
| PiKVM (RasPi 4) | 1 | 64GB (SD) | - | 4GB | PiKVM | KVM |
| TESmart 8 Port KVM Switch | 1 | - | - | - | - | Network KVM (for PiKVM) |
| UniFi UDM Pro Max | 1 | - | 2x16TB HDD | - | UniFi OS | Router & NVR |
| UniFi USW Pro Aggregation | 1 | - | - | - | UniFi OS | 10G/25Gb Core Switch |
| UniFi USW Pro Max 24 PoE | 1 | - | - | - | UniFi OS | 2.5Gb PoE Switch |
| UniFi USP PDU Pro | 1 | - | - | - | UniFi OS | PDU |
| APC SMT15000RM2UNC | 1 | - | - | - | - | UPS |
My MS-A2 workstations are configured with the following hardware:
- Crucial 96GB Kit (48GBx2) DDR5-5600 SODIMM
- Samsung 1.92TB M.2 22x110mm PM9A3 NVMe PCIe 4.0
- Samsung 3.84TB U.2 PM9A3 NVMe PCIe 4.0
- Google Coral M.2 Accelerator A+E Key
Many thanks to my friend @onedrop and all the fantastic people who donate their time to the Home Operations Discord community. Be sure to check out kubesearch.dev for ideas on how to deploy applications or get ideas on what you may deploy.
See the latest release notes.
See LICENSE.
![@bot-blake[bot]](https://avatars.githubusercontent.com/in/311112?s=64&v=4){kind=small}
