Files
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

2.4 KiB

type, title, description, tags, status, generated, verified
type title description tags status generated verified
Decision Full Kubernetes instead of k3s kubeadm installs upstream Kubernetes with containerd, Calico and etcd; k3s is out, at the cost of a bigger control plane.
decision
kubernetes
infra
stable
by at
opencode-go/deepseek-v4.1-flash 2026-10-24T00:00:00Z
by at
human:noel 2026-10-24T00:00:00Z

Decision

The cluster is upstream Kubernetes installed with kubeadm: containerd as the runtime, etcd on the single control-plane node, Calico as the CNI. k3s is not used. Nothing hides the control plane.

Why

  • kubeadm is the installer a hiring team recognises. The components it writes (kube-apiserver, etcd, kube-scheduler, kube-controller-manager, kubelet) are the ones the job talks about.
  • k3s hides those components behind one binary and a SQLite default. The project exists to learn the real thing, not a slimmed-down version.
  • FreeLens, Terraform and kubectl treat both the same, so nothing else in the bundle changes.
  • A full control plane needs roughly 900 MB to 1.2 GB. server0 at 4 GB is tight, so it is upgraded or replaced before release 0.3.0 — see open questions.

Consequences

  • The cluster ships no ingress controller, no load balancer, no metrics-server and no storage provisioner. Caddy stays the entry; metrics-server (HPA) and local-path-provisioner (the tracker's SQLite volume) are installed by the Terraform module.
  • NetworkPolicy comes from Calico, not from k3s' bundled controller.
  • The kubelet refuses to start on a swapped host by default. failSwapOn: false is set explicitly; pods still get no swap, host processes do.
  • Registry credentials move from /etc/rancher/k3s/registries.yaml to containerd's hosts.toml.

Rejected

Option Why not
Keep k3s Fast, but it hides exactly the control plane this project is meant to teach
microk8s Upstream and light, but snap packaging and addons hide the install steps too
k0s Fits 4 GB, but the same "one binary, no etcd" tradeoff as k3s
Managed cluster (k3s cloud, EKS, Hetzner) Costs money every month and removes provisioning from the learning

Details

Provisioning: Terraform. Memory: server budget. Admin access: FreeLens.