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

3.5 KiB

type, title, description, tags, status, generated
type title description tags status generated
Overview Interactive CV on Kubernetes A CV whose life chapters run as real Kubernetes workloads that visitors can knock down and watch recover.
overview
cv
kubernetes
stable
by at
claude-code/claude-opus-5-5 2026-10-11T12:15:30Z

In one sentence

Noel's CV on the apex domain, where every life chapter is a workload on a home Kubernetes cluster (kubeadm, containerd, Calico): visitors push a chapter over and watch it stand up again. The theme is falling down and standing up again.

Two audiences, one page

Audience What they get
HR, 10 seconds Name, role, contact, PDF CV. No interaction needed.
Non-technical visitor A life map of chapters in plain words, a "Push this chapter" button, and a story card after every fall.
Developer The raw live event stream from the cluster: pod states, restarts, recovery times.

The idea in pictures

Kubernetes state Life meaning
Job, Completed Finished chapter (school, 42 piscine)
Deployment, Running and Ready Active chapter
Running, NotReady Exists but unfinished (studies, thesis)
CrashLoopBackOff An attempt that failed and stayed failed, shown as a lesson
restartCount Setbacks survived

Full mapping: chapter states.

How it works, high level

Visitor ─► Caddy (TLS, Terraform) ─► Go gateway ─┬─ serves the Nuxt site (static files)
                                                 ├─ streams live chapter states (SSE)
                                                 └─ forwards "push" to a chapter's /fall
                                                         │
                                         chapter services in namespace `cv`
                                         (one Go image, behavior set by env)

When a chapter is pushed, its process exits, Kubernetes restarts it, and the page shows the real recovery time next to the story of how Noel recovered.

Drill down

Ground rules

  • Learning project, ship small. Each release is a few days of work.
  • No tooling beyond the stack without Noel's approval. The stack is Nuxt, Go, Kubernetes via kubeadm, Terraform, Docker, Snyk, Gitea Actions, release-please, Caddy, k6 and FreeLens.
  • Small server, being enlarged. 2 vCPU, 4 GB today, shared with Gitea; a machine with more RAM is planned before 0.3.0 because the full control plane costs about twice what k3s did. The whole CV is capped at 384Mi. See server budget.
  • No visitor gets Kubernetes API access. Visitors and agents only talk to the gateway; only Noel holds a kubeconfig, used from FreeLens over an SSH tunnel.
  • Failures are lessons, never bugs.

Risks

Risk Mitigation
HR confusion The first screen is conventional and complete on its own. The interactive part is optional.
Spectacle without substance Every state change links to a story card.
Home server downtime Accepted for v1, see decision.
Abuse Cooldowns, global rate limit, no raw cluster access, no visitor-defined k6 scripts.
"Unhealthy" read as incompetence Failures are labeled as lessons.