Production infrastructure patterns on consumer hardware. Proxmox, the MikroTik router, and the k3s cluster are defined in Git and changed through pull requests and ArgoCD, not by hand.
Stack
- Hypervisor: Proxmox VE on Ryzen 7 5825U
- Orchestration: k3s, three nodes (one server, two agents) with ArgoCD GitOps
- Networking: MikroTik RB5009 with a default-drop firewall and VLAN segmentation
- Edge: 2× Raspberry Pi 4B for lightweight DNS and monitoring
- Provisioning: Terraform (Proxmox, MikroTik, Cloudflare)
- Configuration: Ansible with Vault-encrypted secrets
- GitOps: Terraform plan and apply from PR comments on a self-hosted GitHub Actions runner, with a manual approval gate before apply; ArgoCD for Kubernetes workloads
- Backups: Proxmox Backup Server for VMs and LXCs, Velero to Garage S3 with an offsite copy in Cloudflare R2
Running Services
- MetalLB + Traefik for ingress with wildcard TLS (cert-manager + Cloudflare DNS-01)
- Authelia SSO with OIDC for all internal services
- Headscale (self-hosted Tailscale) for remote access
- Prometheus + Loki + Grafana for observability
- Unbound + AdGuard Home with Keepalived for HA DNS
The Ansible layer that orchestrates this stack is documented in Architecting an Enterprise-Grade Homelab, and the network security controls are covered in the Zero-Trust MikroTik firewall and VLAN filtering posts.