Will Anderson
b4b05bfe40
The stale apps/gitea-runner.yaml contained two Deployment manifests that conflicted with the canonical Deployments owned by the gitea-runner-config Argo Application (pointing at k8s/gitea-runner/). Dual ownership caused Argo CD to fight itself — restarting runner pods mid-job and producing the "context canceled" failures on neuron-technologies/dharma-el CI. Canonical Deployments (config-version 2026-05-04-cf-access-public-url, docker.sock, CF Access env, replicas=2 for nt-runner) live in k8s/gitea-runner/deployment.yaml and are managed by gitea-runner-config.
infrastructure
Personal infrastructure-as-code for Legion (k3s home server) and supporting tooling.
| Doc | What it covers |
|---|---|
AGENTS.md |
Full reference: machines, secrets, services, domains, namespaces, common operations |
servers/legion/README.md |
What's running on Legion and how deployment works |
servers/legion/RUNBOOK.md |
Disaster recovery — full restore from scratch |
Quick start
cd servers/legion
direnv allow
terraform plan
terraform apply
Push to servers/ to deploy app changes via Argo CD.