Selected work

A homelab that runs like production

A homelab cluster run entirely from Git, with nothing configured by hand.

Client
Personal platform
Role
Operator

Situation

I run my own tools at home, from Git hosting to monitoring. I run that platform the way I run client platforms: from Git, with nothing configured by hand.

What I did

  • Created the k3s nodes as virtual machines on Proxmox with Terraform, so the cluster can be rebuilt from code.
  • Put every application and the cluster’s own configuration in Git repositories on a self-hosted Gitea.
  • Used Kargo to promote each new version from one stage to the next, and Argo CD to keep the cluster in sync with Git. Argo CD reconciles the state on every restart.
  • Watched the cluster with Prometheus and Grafana.
Homelab GitOps platformGitea holds every app, the cluster configuration and the Terraform code in Git. On one path, Kargo promotes each new version stage by stage, and Argo CD syncs the k3s cluster to Git, also after a restart. On the other path, Terraform creates virtual machines on Proxmox, which host the k3s nodes. The k3s cluster runs every app, from Git hosting to monitoring. Prometheus and Grafana collect metrics from the cluster.
How a change reaches the homelab: from Git, through Kargo and Argo CD, to the k3s cluster on Proxmox.

Result

Nothing in the cluster is configured by hand: every change is a commit, and Argo CD brings the cluster back to what Git describes after any restart.

Tools

  • k3s
  • Proxmox
  • Terraform
  • Gitea
  • Argo CD
  • Kargo
  • Prometheus
  • Grafana

All selected work

Have a similar platform problem? Tell me about it.

Book a 30-minute call