From a41728e99bab655e34af48fb3314eb1cb0d50886 Mon Sep 17 00:00:00 2001 From: jedarden Date: Wed, 3 Jun 2026 22:36:50 -0400 Subject: [PATCH] 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 --- docs/plan/plan.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/plan/plan.md b/docs/plan/plan.md index 0d4b358..e5d321a 100644 --- a/docs/plan/plan.md +++ b/docs/plan/plan.md @@ -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