railiance-cluster/workplans/RAIL-BS-WP-0013-knative-substrate.md
codex b697778132
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Finish Knative substrate workplan
2026-07-27 00:53:28 +02:00

2.3 KiB

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
RAIL-BS-WP-0013 workplan Install and operate the Knative substrate capability financials railiance-cluster finished codex railiance 2026-07-26 2026-07-26 552e55be-4b14-47cc-8680-8bf1ab97f15b

RAIL-BS-WP-0013 - Knative substrate

T01 - Automate the read-only preflight

id: RAIL-BS-WP-0013-T01
status: done
priority: high
state_hub_task_id: "ba2e40b0-ae9f-4917-91f8-d50735510581"

Collect version, node readiness, CRD, ingress, and storage facts without reading secrets. Emit JSON suitable for reef admission evidence.

T02 - Restore or establish agent-reachable API access

id: RAIL-BS-WP-0013-T02
status: done
priority: high
state_hub_task_id: "764de270-321e-4b51-a6ce-5fe1d19dd2d9"

The configured API endpoint 92.205.62.239:6443 timed out on 2026-07-26. Resolve reachability through the sanctioned ops-bridge route and rerun T01.

2026-07-26: Direct API access still timed out, but the configured agent SSH lane reached the cluster-local API and completed the preflight.

T03 - Pin and install Knative Serving

id: RAIL-BS-WP-0013-T03
status: done
priority: high
state_hub_task_id: "89e55bf6-d73d-454c-b6e8-bb1c5c5df7dd"

Select a version compatible with the observed Kubernetes server, pin upstream artifacts by digest, install idempotently, and retain uninstall/rollback state. Do not begin until T01 passes.

2026-07-26: Installed Serving and net-kourier v1.22.0 from checksum-locked assets. Kubernetes v1.35.1 satisfies the release minimum of v1.34. Kourier is ClusterIP-only and the idempotent installer/verifier are repository-owned.

T04 - Verify lifecycle and publish reef evidence

id: RAIL-BS-WP-0013-T04
status: done
priority: high
state_hub_task_id: "170c2524-dd4d-41ec-aafa-e48100a410f6"

Exercise scale-to-zero, cold start, revision traffic, rollback, private visibility, metrics, and failure behavior. Publish versioned evidence to reef-railiance; never infer readiness from successful apply alone.

2026-07-26: Verified private readiness, scale-to-zero, 6276 ms cold activation, second revision readiness, and rollback. Published reef evidence; production approval remains blocked by workload and failure-domain gates.