coulomb/railiance-cluster
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-cluster/install/knative
History
Exact
codex f1a32bd5a7
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Enable Knative fail-closed init gates
2026-07-27 07:18:07 +02:00
..
install.sh Enable Knative fail-closed init gates 2026-07-27 07:18:07 +02:00
README.md Enable Knative fail-closed init gates 2026-07-27 07:18:07 +02:00
release-lock.env Install and verify Knative Serving v1.22 2026-07-26 20:16:30 +02:00
verify.sh Enable Knative fail-closed init gates 2026-07-27 07:18:07 +02:00

README.md

Knative Serving installation

install.sh verifies repository-pinned SHA-256 checksums for the upstream Serving and Kourier v1.22.0 assets before applying them over SSH. It is idempotent. Kourier is kept ClusterIP; public entry through Traefik, DNS, and TLS requires separate reef admission evidence.

The installer enables only Knative's kubernetes.podspec-init-containers feature. Production workloads use init containers for fail-closed admission checks such as verifying that egress policy has reconciled before application code starts.

Run install.sh railiance01, then verify.sh railiance01.

Before workload admission, rollback deletes Kourier, Serving core, then CRDs using the same verified assets. After Knative Services exist, removal requires a workload migration and backup review and is not unattended.