own-proxy decision, terraform provisioner, system diagram, gateway SSE notes, server-budget comment and roadmap 0.4.0 now use Caddy with ACME-managed TLS instead of nginx plus certbot
Packages, swap, k3s, Caddy and DNS are Terraform code; workloads inside the cluster stay with kustomize.
decision
terraform
infra
stable
by
at
claude-code/claude-opus-5-5
2026-10-14T00:00:00Z
by
at
human:noel
2026-10-14T00:00:00Z
Decision
Terraform owns everything outside k3s: server packages, swap, the k3s
install, Caddy (including automatic HTTPS) and the DNS record. Nothing inside the cluster.
Why
The whole system becomes rebuildable from nothing: terraform destroy
then terraform apply, then kubectl apply -k deploy/.
Infrastructure as code is a core work skill; the playground is the place to
learn it on a real, cheap target.
The same files target the home server now and any cloud VM later.
Rejected
Option
Why not
Ansible
Fine, but Terraform also covers DNS and is the more common hire signal
Terraform for k8s workloads
kubectl/helm already own cluster state; two owners fight