Files
OKF_CV_Website/decisions/provision-with-terraform.md
Noel Sabia e022c30527 feat(okf): run on full Kubernetes with FreeLens for admin
k3s is out. The cluster is upstream Kubernetes installed with kubeadm:
containerd, single control-plane etcd, Calico for NetworkPolicy.

- add the cluster decision and the FreeLens decision
- move Terraform from the k3s service to kubeadm, Calico, metrics-server
  and the local-path provisioner
- budget ~900 MB for the control plane and plan a bigger machine before 0.3.0
- note kubelet failSwapOn and containerd hosts.toml
- rename 0.3.0 and commit the 0.2.0 done-when to the new stack
- update the German learning plan
2026-10-24 19:02:17 +02:00

1.3 KiB

type, title, description, tags, status, generated, verified
type title description tags status generated verified
Decision Provision the server with Terraform Packages, swap, kubeadm, 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 Kubernetes: server packages, swap, containerd, the kubeadm control plane, Caddy (including automatic HTTPS) and the DNS record. It bootstraps the namespace and the cluster addons once; the workloads themselves stay with kustomize.

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
Manual server setup Works once, impossible to demo or recover

Details

See terraform provisioning.