type, title, description, tags, status, generated
| type |
title |
description |
tags |
status |
generated |
| Reference |
Chapter states |
How each Kubernetes primitive and state maps to a meaning in Noel's life story. |
|
stable |
| by |
at |
| claude-code/claude-opus-5-5 |
2026-10-11T12:15:30Z |
|
Mapping
| Kubernetes |
Meaning |
Example |
Release |
| Job, Completed |
Finished chapter |
School, 42 piscine |
v1 |
| Deployment, Running and Ready |
Active, stable chapter |
PreZero, Example |
v1 |
| Running, NotReady |
Exists, unfinished |
Ongoing studies, thesis |
v1 |
| CrashLoopBackOff |
Failed and stayed failed |
Abandoned projects |
v1 |
restartCount |
Setbacks survived |
"fell 3×, stood up 3×" |
v1 |
| Replicas, HPA scale-up |
Load carried, growth under pressure |
Team lead, two businesses |
Phase 3 |
| Rolling update |
Pivot or reinvention |
Career switch |
Not planned yet |
Finished chapters are Jobs because they complete. Current chapters are
Deployments because they must stay alive.
Narrative rules
- Every fall shows a story card: what went wrong and what got Noel back up.
- The recovery time shown is real, measured in seconds.
- Permanently failed chapters show a lesson card, not a recovery.
- Failures are labeled as lessons, never as bugs.