railiance-cluster/workplans/ADHOC-2026-07-27.md
codex db7860ec2e
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
fix(workplans): correct double-prefixed ad-hoc identifier
The requalification script applied its generic ADHOC rule before its
RAIL-BS-ADHOC rule, producing RAIL-BS-RCLUSTER-WP-ADHOC-2026-07-27. My
validator checked the identifier's shape and not its prefix, and the canon
pattern accepts arbitrary prefix segments, so it passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-28 11:05:27 +02:00

32 lines
897 B
Markdown

---
id: RCLUSTER-WP-ADHOC-2026-07-27
type: workplan
title: "Knative fail-closed init-container support"
domain: financials
repo: railiance-cluster
status: finished
owner: codex
topic_slug: railiance
created: "2026-07-27"
updated: "2026-07-27"
---
# RCLUSTER-WP-ADHOC-2026-07-27
## Enable and verify Knative init containers
```task
id: RCLUSTER-WP-ADHOC-2026-07-27-T01
status: done
priority: high
```
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`.