docs(recovery): trigger cd readback after api cap
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Failing after 21s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Failing after 21s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped
This commit is contained in:
@@ -44,6 +44,7 @@
|
||||
|
||||
**下一步**:
|
||||
- 推 Gitea main 後等 ArgoCD 套用 `replicas=1` recovery cap,讀回 API / Web / Worker Ready、production workbench runtime/desired tag 等於最新 deploy marker;後續 P0 必須修 DB role limit / pool budget 後恢復 API `replicas=2`。
|
||||
- `48d2d0f` 使用 `[skip ci]` 是為了先讓 ArgoCD source truth 接住 live recovery cap;完成後仍必須推一個正常 CD commit,讓 Actions 綠燈、image tag 與 latest main/deploy marker 重新一致。
|
||||
|
||||
## 2026-07-01 — 15:25 Gitea live recovery after 110 Docker/control-plane failure
|
||||
|
||||
|
||||
Reference in New Issue
Block a user