🏡 High-Availability K3s Cluster for Homelab — featuring kube-vip for HA control-plane, MetalLB for LoadBalancer services, Pi-hole for DNS/ad-blocking, and Caddy as Ingress controller. Built on bare metal with mixed ARM/AMD nodes.
  • HTML 53.7%
  • Shell 31.2%
  • HCL 7.4%
  • Smarty 7.1%
  • Dockerfile 0.6%
Find a file
Yusuf Taylan Yuksel 38c14600a8
All checks were successful
Test Action / test (push) Successful in 11s
docs: add Forgejo API + CI workflow reference to homelab-k3s skill
2026-08-22 23:52:42 +03:00
.forgejo/workflows ddns: automate config-cloudflare-ddns secret via deploy-ddns workflow (Refs #42) 2026-08-02 21:37:14 +03:00
.kiro docs: add Forgejo API + CI workflow reference to homelab-k3s skill 2026-08-22 23:52:42 +03:00
docs/proxmox update pve lookup repo 2025-12-30 12:09:48 +02:00
k3s-ha-cluster remove stirling-pdf and changedetection references (superseded by bentopdf, #48) 2026-08-22 23:48:48 +03:00
terraform remove deprecated services (keycloak, nextcloud, paperless-ngx, iperf3); fix stale doc links (Refs #23, #26) 2026-08-22 23:28:09 +03:00
.gitignore portfolio: add workflow for the deployment 2026-07-05 13:56:58 +03:00
LICENSE initial commit 2025-07-21 01:01:39 +03:00
README.md README: update main readme 2026-03-07 18:52:54 +02:00

Maestro homelab

🏡 High-Availability K3s Cluster for Homelab

This is a bookkeeping for setup of my infrastucture and services. It features kube-vip for HA control-plane, MetalLB for LoadBalancer services, Pi-hole for DNS/ad-blocking along with unbound, and Caddy for reverse proxy and etc.

🖥️ Physical Lab Inventory

A concise overview of the hardware powering this homelab:

  • 💻 GMTec Mini PC Intel N150, 16GB DDR4 RAM, 256GB NVMe SSD

  • 💻 Beelink S13 Mini PC Intel N150, 16GB DDR4 RAM, 500GB M.2 SSD

  • 🍓 Raspberry Pi 4B 8GB RAM, 256GB microSD card

  • 📶 GL.inet Flint 3e - OpenWRT Wifi-7 Router, with 2.5gigabit ports

🧱 Infrastructure with Proxmox + Terraform

I use Proxmox VE to manage bare-metal virtualization and Terraform to automate VM provisioning:

🖥️ VMs are provisioned on multiple nodes using Proxmox's API.

📦 Each VM is bootstrapped with cloud-init templates.

⚙️ Terraform handles:

    VM creation

    Resource allocation (CPU, memory, disk)

    SSH key injection

    Network config

Directory: terraform

☸️ High-Availability K3s Cluster

K3s HA setup is designed for simplicity, resilience, and a rich self-hosted ecosystem:

🏗️ Core Infrastructure & Storage

  • 🛢️ External MariaDB: Runs on the Proxmox host to serve as K3s datastore.
  • 🧠 kube-vip: Provides a virtual IP (VIP) for easy access to the K3s API.
  • 💾 Longhorn: Distributed block storage providing persistent, replicated volumes across the cluster.

🌐 Networking & Security

  • 🧲 MetalLB: Manages service-level LoadBalancer IPs for internal cluster services.
  • 🌍 Caddy Ingress: Handles clean, domain-based routing and automatic SSL for all web services.
  • 👮 CrowdSec: Integrates directly with Caddy to detect and block known malicious IPs and brute-force attacks.
  • 🧅 Pi-hole + Unbound: Runs bare metal rpi4 to serve fast local DNS resolution and network-wide ad blocking.
  • 🔄 Cloudflare DDNS: Automatically updates my public Cloudflare DNS entries by cron run.
  • 🔒 Tailscale VPN: Deployed on a bare-metal Raspberry Pi 4 node for secure, zero-trust remote network access.

🛠️ DevOps & Management

  • 🐙 Forgejo Git Server: Self-hosted Git repository complete with local actions runners to automatically deploy configuration changes.
  • 💻 Termix: Provides a web-based terminal for easy remote access to nodes (accessible securely via Tailscale).

🏠 Media & Dashboards

  • 📊 Homer: A clean, static dashboard for quick access to all homelab services.
  • 🍿 Media Stack: The full Arr suite paired with Jellyfin for internal media management and streaming.

Directory: /k3s-ha-cluster/


🔗 Inspiration & References

This project draws inspiration and practical ideas from the following excellent resources. Many thanks to their authors for sharing their knowledge with the community: