ACTIVE 2026

WoNQstaq_v3

Three dedicated Hetzner servers running a K3s + Ceph RBD cluster with Git, registry, CI/CD, observability, and a fat replicated storage yard underneath it all.

WoNQstaq_v3 project artwork

About This Project

WoNQstaq_v3 is the current self-hosted backbone: three dedicated Hetzner machines kept close enough for sub-millisecond east-west traffic, but split enough physically to reduce shared-failure stupidity. On top of that sits a K3s + Ceph cluster with GitOps and operator tooling for the rest of the stack.

Current Highlights

  • 3 dedicated servers spread across separate rooms in one Hetzner datacenter
  • K3s + Ceph triple-node cluster with replica_size 2
  • 96TB raw HDD + 3TB raw NVMe, landing around ~48TB bulk and ~1.5TB fast replicated net capacity
  • Git / registry / CI / CD stack with Forgejo, Zot, Drone, and ArgoCD
  • Prometheus-based observability and service-level deployment automation
  • Cluster hosts public and private yard services including Rikketik and WoNQ workloads

Cluster Shape

The setup is intentionally simple in physical count and serious in capability: three dedicated nodes, close enough for fast cluster traffic, separated enough to avoid one dumb local failure taking all three out at once.

What the Attached Tarball Confirms

  • Cilium networking and egress policies are present
  • Ceph-backed storage classes and PVC usage show up all over the manifests
  • Forgejo, Drone, ArgoCD, and Zot-related deployment material exists in the stack
  • The repo also contains workload directories for public-facing sites and internal services riding on top of the cluster

Why It Matters

This is the yard where the other projects actually live. It is not just a lab diagram — it is the physical and orchestration layer that lets the public sites, media systems, chat tooling, and internal services run on owned infrastructure.

Tech Stack

K3sCeph RBDCiliumForgejoZotDroneArgoCDPrometheus