coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add Railiance canary chart template

Browse source
This commit is contained in:
tegwick 2026-06-27 16:38:00 +02:00
parent a23b3327fc
commit c89d6fad07
6 changed files with 408 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/RAIL-BS-WP-0006-staged-promotion-lifecycle.md
View file

@ -160,7 +160,7 @@ Expected behavior:
```task
id: RAIL-BS-WP-0006-T05
status: todo
status: done
priority: high
state_hub_task_id: "47b8cd47-99c7-4f31-a147-ea16afde7217"
```
@ -179,6 +179,15 @@ Minimum requirements:
**Done when:** a canary deployment can be created without hand-editing cluster
resources.
2026-06-27: Updated generated overlay charts for Stage 2 canaries. The
scaffold now emits stable/canary release identities, isolated canary ingress by
default, optional Traefik weighted routing, Prometheus-compatible annotations,
HTTP probes, conservative single-node resource limits, rollback labels,
separate Stage 2/Stage 3 values, and `tests/stage2-template.sh`. Verified a
fresh Forgejo overlay with schema validation, Stage 1 run, and Stage 2 scaffold
checks; Helm rendering was skipped because Helm is unavailable in this
environment.
---
### T06 - railiance deploy --stage 2 and observation tooling