3a5432270e
install.sh now renders the checksum-verified upstream assets through kustomize overlays: CRDs first and verbatim, then serving-core and kourier with the six CPU requests lowered live on 2026-09-21, the Kourier Service as ClusterIP and the Envoy image pinned. verify.sh checks the requests read-only, and tests/test_knative_render.py proves the render offline against upstream and rail-knative's declaration. Not run against the cluster. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 63291@bnt-lap001 Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
17 lines
1.1 KiB
Bash
Executable file
17 lines
1.1 KiB
Bash
Executable file
#!/usr/bin/env bash
|
|
set -euo pipefail
|
|
root="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
target="${1:-railiance01}"
|
|
stage="$(mktemp -d)"
|
|
trap 'rm -rf "$stage"' EXIT
|
|
# Checksum-verified upstream assets, rendered with the declared CPU requests
|
|
# (rail-knative substrate/v1.22.0), Kourier ClusterIP and the Envoy pin.
|
|
"$root/render.sh" "$stage"
|
|
# CRDs first and separately: serving-core.yaml repeats one of them.
|
|
ssh "$target" kubectl apply -f - < "$stage/crds.yaml"
|
|
ssh "$target" kubectl apply -f - < "$stage/serving-core.rendered.yaml"
|
|
ssh "$target" kubectl wait --for=condition=Available deployment --all -n knative-serving --timeout=300s
|
|
ssh "$target" kubectl apply -f - < "$stage/kourier.rendered.yaml"
|
|
ssh "$target" kubectl patch configmap/config-network -n knative-serving --type merge -p '{"data":{"ingress-class":"kourier.ingress.networking.knative.dev"}}'
|
|
ssh "$target" kubectl patch configmap/config-features -n knative-serving --type merge -p '{"data":{"kubernetes.podspec-init-containers":"enabled"}}'
|
|
ssh "$target" kubectl wait --for=condition=Available deployment --all -n kourier-system --timeout=300s
|