← Back home

Infrastructure

nodes online
pods running
k3s nodes
4
live products
Live telemetry, pulled from the cluster — refreshes every 30s.

Physical Network

All physical machines sit behind OPNsense on a home LAN. Internet traffic leaving the homelab goes exclusively through a WireGuard VPN on the main server — nothing else has a direct outbound internet path.

Internet
WAN
ISP Router
DHCP / gateway
OPNsense
firewall
LAN
physical nodes
HP EliteDesk 800 G2
Ubuntu
  • ·Media stack
  • ·gpu-proxy
  • ·k3s control plane
Gaming PC — RTX 5070
Windows 11
  • ·Ollama (RTX 5070)
  • ·GPU inference
Beelink ME Pro 2 · N95
TrueNAS Scale
  • ·ZFS mirror RAID1
  • ·4 TB storage
  • ·NFS for k3s

Tailscale Overlay

Tailscale connects the remote nodes — a monitoring Pi and two cloud workers — back to the homelab without any firewall rules or VPN tunnels to configure. Every machine joins the same tailnet, reachable from anywhere as one flat private network.

Raspberry Pi 4
Raspberry Pi OS
Monitoring
  • ·Prometheus
  • ·Grafana
  • ·Alertmanager
OCI VM.Standard.A1 (ARM)
Ubuntu
k3s worker 1
  • ·k3s agent
OCI VM.Standard.A1 (ARM)
Ubuntu
k3s worker 2
  • ·k3s agent

k3s Cluster

A lightweight Kubernetes cluster spanning the homelab and cloud. The main server acts as control plane; two free-tier ARM workers provide enough capacity to run this site, several web apps, and supporting services.

HP EliteDesk 800 G2
control-plane
OCI VM.Standard.A1 (ARM)
worker 1
OCI VM.Standard.A1 (ARM)
worker 2