From 774310b205b8e6891c865e62c2fd75aaf361e6ea Mon Sep 17 00:00:00 2001 From: mpabi Date: Sun, 12 Apr 2026 18:39:38 +0200 Subject: [PATCH] docs(plan): record sequential canary rollout fix --- doc/migration-todo.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/migration-todo.md b/doc/migration-todo.md index 8798bcd..2633a7c 100644 --- a/doc/migration-todo.md +++ b/doc/migration-todo.md @@ -371,6 +371,8 @@ Date: `2026-04-12` - In progress. - Initial validation on `2026-04-12`: after the DLOB hot/all-path rollout, sampled Agave slot lag on `sol` at `0` versus `https://api.mainnet-beta.solana.com`, with local health still reporting `ok`. +- Done on `2026-04-12`: adjusted the canary rollout model to match the namespace guardrails by switching deployments to `RollingUpdate { maxSurge: 0, maxUnavailable: 1 }`, adding explicit low CPU limits to `api-token-seed`, and making the workflow restart the surface sequentially instead of all at once. +- Done on `2026-04-12`: after the sequential smoke rollout on `sol`, all canary deployments returned to `Available=1/1`, `trade-api /v1/ticks` and `/v1/chart` returned data, and the validator still reported `lag=0`, `health=ok`. ### 24. Keep `mevnode_bot` as a rollback target until the new stack is stable