docs(plan): note CF Pages serves replay data at initial volumes (<20k files)

R2 warm cache tier removed. Cloudflare Pages holds replay data directly
until file count approaches 20k, at which point storage strategy should
be reassessed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
jedarden 2026-06-03 22:36:50 -04:00
parent c1cbefead1
commit a41728e99b

View file

@ -1648,6 +1648,8 @@ Key principles:
- **B2 as single storage layer** — B2 stores all replays, match metadata,
thumbnails, bot cards, and evolution status. Served directly via Cloudflare
CDN (Bandwidth Alliance = zero egress fees). No warm cache tier needed.
Replay files are served via Cloudflare Pages at initial volumes (<20k files);
reassess if object count approaches that threshold.
- **GitOps via ArgoCD** — all K8s manifests are committed to git and synced
by ArgoCD. Never apply manifests directly with `kubectl`.
- **Argo Workflows for CI** — container image builds and static site builds