trade-next/trade-gitops
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(sol): serialize canary rollouts under quota
All checks were successful
deploy-trade-r001-canary / apply (push) Successful in 6m46s
Details

Browse Source
This commit is contained in:
mpabi
2026-04-12 18:39:31 +02:00
parent 2e909026a7
commit c76eb7d5f3
10 changed files with 60 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
environments/sol/trade-r001-canary/README.md
View File

@@ -54,6 +54,7 @@ Minimal canary namespace for migration baseline `R001` on `sol`.
before it waits for `Hasura`, `trade-api`, `trade-frontend`, `trade-ingestor`, and the DLOB hot/all-path deployments to become healthy.
- The canary `trade-ingestor` now follows the live `R001` path on `sol`: it reads `dlob_hot_derived_latest` first for hot markets and falls back to `dlob_all_derived_latest`.
- `api-token-seed` restores the frontend read token in `api_tokens`, so `trade-api` and `trade-frontend` can be validated against the reconstructed derived tables after each deploy.
- Canary deployments use `RollingUpdate` with `maxSurge=0` and `maxUnavailable=1`, and the workflow restarts them sequentially, because the namespace `limits.cpu=6` guardrail does not tolerate surge-based restarts of the full surface at once.
## Operator Flow