Files
OKF_CV_Website/overview.md
T

75 lines
3.2 KiB
Markdown

---
type: Overview
title: Interactive CV on k3s
description: A CV whose life chapters run as real Kubernetes workloads that visitors can knock down and watch recover.
tags: [overview, cv, k3s]
status: stable
generated: { by: claude-code/claude-opus-5-5, at: 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 k3s cluster: 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](/chapters/state-mapping.md).
# How it works, high level
```
Visitor ─► Cloudflare Tunnel ─► 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
* [System architecture](/architecture/system.md) - every component and how they connect.
* [Roadmap](/roadmap.md) - small releases, each a few days of work.
* [Decisions](/decisions/) - what we chose and what we cut.
* [Open questions](/decisions/open-questions.md) - what is still undecided.
# 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, k3s, Snyk, Gitea Actions, release-please, Cloudflare Tunnel, and k6.
- **Small server.** 2 vCPU, 4 GB, shared with Gitea. The whole CV is capped at 384Mi. See [server budget](/architecture/server-budget.md).
- **Nobody gets Kubernetes API access.** Visitors and agents only talk to the gateway.
- **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](/decisions/accept-downtime-v1.md). |
| Abuse | Cooldowns, global rate limit, no raw cluster access, no visitor-defined k6 scripts. |
| "Unhealthy" read as incompetence | Failures are labeled as lessons. |