The railiance operations rail for dynamic knative workloads.
Find a file
tegwick affe67a4bc RAIL-KNATIVE-WP-0003: applied on railiance01, finished
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-21 21:07:29 +02:00
declarations Promote derived rail to verified 2026-07-26 20:16:31 +02:00
docs RAIL-KNATIVE-WP-0003: cap Knative HPAs for one node, trim substrate CPU requests to 60m 2026-10-21 08:40:35 +02:00
examples Add generic Knative service contract 2026-07-26 14:14:26 +02:00
registry docs(reuse): establish reviewed NetKingdom security capabilities 2026-10-14 06:43:49 +02:00
substrate/v1.22.0 RAIL-KNATIVE-WP-0003: cap Knative HPAs for one node, trim substrate CPU requests to 60m 2026-10-21 08:40:35 +02:00
tests RAIL-KNATIVE-WP-0003: cap Knative HPAs for one node, trim substrate CPU requests to 60m 2026-10-21 08:40:35 +02:00
workplans RAIL-KNATIVE-WP-0003: applied on railiance01, finished 2026-10-21 21:07:29 +02:00
.custodian-brief.md chore: sync State Hub ids, generated briefs and work records 2026-10-21 09:12:03 +02:00
.gitignore Ignore generated Python test artifacts 2026-07-26 14:15:01 +02:00
.repo-classification.yaml Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
AGENTS.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
CLAUDE.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
INTENT.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:47:12 +02:00
README.md Close Knative CPU request handoff with installer evidence 2026-09-27 18:01:25 +02:00
SCOPE.md Bootstrap derived Knative rail 2026-07-26 13:35:05 +02:00
WORK-RECORDS.md chore: sync State Hub ids, generated briefs and work records 2026-10-21 09:12:03 +02:00

rail-knative

Derived Railiance execution rail for Knative Serving workloads.

This rail inherits the versioned rail-kubernetes common workload contract and owns only Knative-specific activation, scale-to-zero, revision, traffic, cold-start, and rollback semantics.

The declaration records verified readiness, backed by the 2026-07-26 lifecycle evidence on reef-railiance. This is not production approval.

The substrate runbook describes the declared CPU requests consumed by the railiance-cluster installer.