These workplans exist only in the retired local hub. Their random pre-ADR-007 identifiers are refused by C-06 as stale references, so they cannot be registered. Deriving from the canonical record id takes no identity from anything: central does not hold them and the old ids die with the cache. Records central already holds were deliberately left untouched. Refs CUST-WP-0068-T06 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
1,007 B
1,007 B
| id | type | title | domain | repo | status | owner | topic_slug | created | updated | state_hub_workstream_id |
|---|---|---|---|---|---|---|---|---|---|---|
| RAIL-BS-ADHOC-2026-07-27 | workplan | Knative fail-closed init-container support | financials | railiance-cluster | finished | codex | railiance | 2026-07-27 | 2026-07-27 | 9a77bc91-f457-5545-996f-04f49707f54b |
RAIL-BS-ADHOC-2026-07-27
Enable and verify Knative init containers
id: RAIL-BS-ADHOC-2026-07-27-T01
status: done
priority: high
state_hub_task_id: "fd47a55b-233d-53ec-8005-7e24b2a98e42"
Enable only kubernetes.podspec-init-containers in Knative
config-features, persist the idempotent installer patch, and assert it in
the verifier. This supports fail-closed workload admission after asynchronous
NetworkPolicy reconciliation.
2026-07-27: Enabled the feature on railiance01 and validated a
rapp-qonto Knative Service containing a restricted init container through
the live admission webhook. A disposable same-policy pod proved
gate=passed before application=admitted.