My Home Operations Repository ... managed with Flux, Renovate, and GitHub Actions 🤖
Tool
Purpose
flux Operator that manages the kubernetes cluster based on the Git repository
go-task A task runner / simpler Make alternative written in Go
sops Encrypts kubernetes secrets with Age
Node
Hostname
RAM
Storage
Function
Operating System
Intel NUC13ANHI5
K8s-M01
64GB
OS-Disk 512GB, Ceph-Disk 4TB
Kuberneter Master
Talos
Intel NUC13ANHI5
K8s-M02
64GB
OS-Disk 512GB, Ceph-Disk 4TB
Kuberneter Master
Talos
Intel NUC13ANHI5
K8s-M03
64GB
OS-Disk 512GB, Ceph-Disk 4TB
Kuberneter Master
Talos
Node
Hostname
RAM
Storage
Function
Operating System
Intel NUC12WSKI5
K8s-U01
16GB
OS-Disk 256GB
Kuberneter Master
Talos
Node
Hostname
RAM
Storage
Function
Operating System
Self-Build Server
Proxmox01
64GB
6 x 20TB HDD (data), 2 x 1TB NVME (cache), 2 x 1TB NVME (vms)
VM Host and NAS
Proxmox 8.2
Self-Build Server
Proxmox02
256GB
5 x 8TB HDD (data), 2 x 1TB SSD (vms)
Backup Server
Proxmox 8.2
Vendor
Model
Function
Unifi
USW Aggregation 8 Port
Main Rack Switch and 10G SFP+
Unifi
USW Enterprise 48 PoE
Second Rack Switch with RJ45, connected with 10G SFP+
Unifi
USW Pro Max 16
Livingroom Switch for TV and everything else, connected with 10G SFP+
Unifi
UDM-SE
Main Router connected to USW Aggregation with 10G SFP+
Kubernetes nodes are on their own VLAN which has access to the NAS.
While most of my infrastructure and workloads are self-hosted I do rely upon the cloud for parts that are hard to self-host.
