Update stabilization checkpoint after canary template
This commit is contained in:
@@ -44,7 +44,7 @@ Active registered workstreams with open work:
|
||||
| cust-wp-0049 | 1 wait, 5 done | Access lane is ready; live bootstrap needs approved admin execution. |
|
||||
| activity-wp-0016 | 1 wait, 2 progress, 5 todo, 2 done | Daily-triage output robustness needs live deploy/smoke evidence. |
|
||||
| three-phoenix-ha-cluster | 7 todo | Target HA substrate is planned but not executed. |
|
||||
| staged-promotion-lifecycle | 6 todo, 1 done | Promotion discipline needed before broad production cutovers. |
|
||||
| staged-promotion-lifecycle | 2 todo, 5 done | Promotion discipline needed before broad production cutovers. |
|
||||
| rail-ho-wp-0005 | 11 todo, 1 progress | Forgejo production migration needs human design and cutover decisions. |
|
||||
| cust-wp-0045-cutover-runbook | 0 tasks | Registered runbook is appearing as an active no-task workstream. |
|
||||
| net-wp-0020 | 2 wait, 1 todo, 2 done | OpenBao unseal custody models still need operator profile decisions. |
|
||||
@@ -295,8 +295,8 @@ Progress 2026-06-27 staged promotion:
|
||||
rollback, and human approval gates.
|
||||
- `make fix-consistency REPO=railiance-cluster` passed with pre-existing
|
||||
C-12 warnings and synced the T02 status into State Hub.
|
||||
- Next staged-promotion picks are T04/T05 command and canary template
|
||||
implementation; T03 overlay repo pattern is now complete.
|
||||
- T02 through T05 are complete; the next staged-promotion pick is T06
|
||||
deploy/observe tooling.
|
||||
|
||||
Progress 2026-06-27 staged promotion T03:
|
||||
|
||||
@@ -331,6 +331,20 @@ Progress 2026-06-27 staged promotion T04:
|
||||
- `make fix-consistency REPO=railiance-cluster` passed with pre-existing
|
||||
C-12 warnings and synced the T04 status into State Hub.
|
||||
|
||||
Progress 2026-06-27 staged promotion T05:
|
||||
|
||||
- Completed `RAIL-BS-WP-0006-T05` in `/home/worsch/railiance-cluster`.
|
||||
Generated overlays now include a Stage 2 canary Helm template with
|
||||
stable/canary release identities, isolated ingress by default, optional
|
||||
Traefik weighted routing, Prometheus annotations, HTTP probes, conservative
|
||||
resource limits, rollback-safe Stage 2/Stage 3 values, and
|
||||
`tests/stage2-template.sh`.
|
||||
- Verified a fresh generated Forgejo overlay with schema validation,
|
||||
`tests/stage1.sh`, `tests/stage2-template.sh`, and `bin/railiance run`.
|
||||
Helm rendering was skipped because Helm is unavailable in this environment.
|
||||
- `make fix-consistency REPO=railiance-cluster` passed with pre-existing
|
||||
C-12 warnings and synced the T05 status into State Hub.
|
||||
|
||||
## Task: Decide State Hub Migration Strategy
|
||||
|
||||
```task
|
||||
|
||||
Reference in New Issue
Block a user