Add isolated ops-warden warn pin (FLEX-WP-0016); FLEX-WP-0007 stays finished
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

policy.enabled cannot flip against the user-engine or tenant-engine
bindings. Helm release flex-auth-ops-warden rev 1 serves the production
registry in warn. Workstation warden sends no caller token; enforce and
the yaml flip stay ops-warden's.
This commit is contained in:
tegwick 2026-08-19 14:50:04 +02:00
parent c48c696387
commit 259f8a20a6
6 changed files with 142 additions and 2 deletions

View file

@ -12,6 +12,7 @@ kubectl path; this overlay is the sanctioned shape.
| `charts/flex-auth/` | One Deployment + Service + NetworkPolicy per release |
| `values/tenant-engine.yaml` | Production pin for `flex-auth-tenant-engine` |
| `values/user-engine.yaml` | Production pin for `flex-auth-user-engine` |
| `values/ops-warden.yaml` | Isolated warn pin for ops-warden signing policy (FLEX-WP-0016) |
| `values/stage2-canary.yaml` | Isolated canary `flex-auth-canary` (no consumer ingress) |
| `values/stage3-production.yaml` | Stage 3 values for that same isolated canary release |
| `tests/stage1.sh` | Local render of every values file |