[ Blog ] · 2 Sept 2026 · 1 min read

What running my own Kubernetes cluster taught me

Notes from moving AirWave, a real-time audio platform, onto a self-managed Kubernetes cluster with GitLab CI and Argo CD.

  • Kubernetes
  • GitOps
  • Argo CD
  • DevOps

AirWave started on a single server. Once communities grew into the thousands, one busy evening could slow down everything else on the box.

Split the work by what it needs

Audio is sensitive to latency and noisy neighbours. The API is not. I moved audio nodes onto separate Hetzner machines and kept core services on OVHcloud, so a spike in live sessions never slows down the API.

Make deploys boring

Every merge to main is built by GitLab CI and rolled out by Argo CD. The cluster state lives in Git, so a rollback is a revert, not a late night.

Keep side effects off the hot path

Payments and vote rewards go through RabbitMQ. If a payment provider is slow, playback does not notice.

Small things that matter

Tailscale links the nodes on a private network, Nginx and Cloudflare sit in front, and Infisical holds every secret, so nothing sensitive lives in the repository.

Building something similar?