Board game v2 migration: one client, per-game runtimes
Sixteen board games moved to /v2 by sharing the client shell and splitting rules into stateless per-game services.
5 posts tagged with kubernetes. This index aggregates both frontmatter tags: entries and inline #kubernetes mentions.
Sixteen board games moved to /v2 by sharing the client shell and splitting rules into stateless per-game services.
This entire blog series was drafted by Claude inside a sandboxed pod; the sandbox got rebuilt three times — Docker, mitm plus credential proxy, then a K8s pod — to make that safe.
An AlphaZero-style pipeline for the augmented chess engine ran into 512Mi pod limits, and the fix taught me the difference between liveness and readiness probes.
Multiplayer games forced a staging branch and a UI for trust — FluxCD kept writing because ArgoCD cannot decrypt SOPS.
Four weeks took a raw k3s box to 14 Knative functions, FluxCD GitOps, and sub-second cold starts — the layering order that made it work.