... managed with Flux, Renovate, Swearing and GitHub Actions 🤖
This is a mono repository for my home infrastructure and Kubernetes cluster. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Kubernetes, TalosCTL, k9s, Flux, Renovate, and GitHub Actions.
If you want to try and follow along with how I built my cluster and with some of the practices I use please check out the amazing template here:
- actions-runner-controller: Self-hosted Github runners.
- cert-manager: Creates SSL certificates for services in my cluster.
- cilium: Internal Kubernetes container networking interface.
- cloudflared: Enables Cloudflare secure access to certain ingresses.
- external-dns: Automatically syncs ingress DNS records to a DNS provider.
- external-secrets: Managed Kubernetes secrets using 1Password Connect.
- ingress-nginx: Kubernetes ingress controller using NGINX as a reverse proxy and load balancer.
- rook: Distributed block storage for peristent storage.
- sops: Managed secrets for Kubernetes and Terraform which are commited to Git.
- volsync: Backup and recovery of persistent volume claims.
My cluster is Talos provisioned baremetal on Minisform MS-01 12900H's utilizing Thunderbolt Ring Networking for Rook Ceph
Flux watches the cluster in 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/${cluster}/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 watches my entire repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged Flux applies the changes to my cluster.
This Git repository contains the following directories under Kubernetes.
📁 kubernetes
├── 📁 main # main cluster
│ ├── 📁 apps # applications
│ ├── 📁 bootstrap # bootstrap procedures
│ ├── 📁 flux # core flux configuration
│ └── 📁 templates # re-useable componentsThis is a high level diagram of how my kubernetes infrastructure is setup
| Device | Count | OS Disk Size | Ram | Operating System | Purpose |
|---|---|---|---|---|---|
| Dell Poweredge R730 | 1 | 2x 2TB Raid1 ZFS | 128GB | Proxmox | Virtualization Host |
| Minisform MS-01 | 3 | 1x 1TB M.2 + 1x1.98TB U.2 | 96GB | TalosIS | Kubernetes Nodes |
| Unifi Dream Machine Pro | 1 | - | - | - | Router / FW DHCP Main Lan |
| Unifi US 24 250w PoE | 1 | - | - | - | PoE for APs etc (1Gbe) |
| Unifi US 48 G1 | 1 | - | - | - | Primary Switch (1Gbe) |
| Unifi U6 Lite | 3 | - | - | - | Wirless Access Points (PoE) |
| Eaton 5s 850 (510w) | 1 | - | - | - | UPS for Servers |
| PiKVM 4 Plus | 1 | - | - | - | IP KVM Interface |
| Ezcoo EZ-SW41HA-KVMU3P | 1 | - | - | - | KVM Switch |
| Woieyeks HDMI Adapter | 4 | - | - | - | 4K HDMI EDID Emulator Passthrough Adapter |
| Device | Count | OS Disk Size | Data Disk Size | CPU | RAM | Operating System | Purpose |
|---|---|---|---|---|---|---|---|
| Stormwind | 1 | 40GB | - | 02c | 02GB | Windows Server 2022 | DNS / DHCP |
| Citadel | 1 | 32GB | 2x 1.98TB U.2 SLOG, 1x 1.98TB U.2 Cache, 3x 22TB Disks ZFS X1 | 04c | 02GB | Windows Server 2022 | TrueNas Scale |
| rclone-proxmox | 1 | 08GB | - | 01c | 01GB | Ubuntu (lxc) | Sync Proxmox backups to Backblaze B2 |
Thanks to all the people who donate their time in the Home Operations and TechnoTim Discord Communities for all of their support. Special Shout out to my friend and colleague Kevin Durbin
See my awful commit history
See LICENSE