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

feat(canary): add ingestor rollout on sol
Some checks failed
deploy-trade-r001-canary / apply (push) Failing after 56s
Details

Browse Source
This commit is contained in:
mpabi
2026-04-12 17:34:03 +02:00
parent 6672e1043d
commit b8f1303e66
6 changed files with 300 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -7,7 +7,7 @@ Minimal canary namespace for migration baseline `R001` on `sol`.
- Reserve a dedicated namespace for the first reconstructed trade deployment.
- Put hard upper bounds on namespace-level CPU, memory, object count, and PVC growth before application manifests land.
- Verify that workloads in the namespace can resolve and reach the shared `trade-infra` services for `Postgres` and `Redis`.
- Recreate the `R001` application surface in a controlled way: `Hasura`, `trade-api`, and `trade-frontend`.
- Recreate the `R001` application surface in a controlled way: `Hasura`, `trade-api`, `trade-frontend`, and the first canary `trade-ingestor` path.
## Current Guardrails
@@ -43,7 +43,9 @@ Minimal canary namespace for migration baseline `R001` on `sol`.
- The canary workflow re-runs:
- `postgres-migrate`
- `hasura-bootstrap`
before it waits for `Hasura`, `trade-api`, and `trade-frontend` to become healthy.
before it waits for `Hasura`, `trade-api`, `trade-frontend`, and `trade-ingestor` to become healthy.
- The current canary `trade-ingestor` is intentionally pinned to the schema already reconstructed on `sol` and reads from `dlob_stats_latest`.
- The exact live `R001` ingestor path that reads `dlob_*_derived_latest` remains a follow-up substep after the DLOB writer chain is reconstructed.
## Operator Flow