ci: add cluster-free manifest validation
infra-ci / manifests (push) Failing after 3s

- add .gitea/workflows/ci.yml with no secrets and no cluster writes
- extract static guardrails to scripts/check_manifests.py
- add gate1-check STATIC_ONLY=1 for CI without a kubeconfig
- add numeric fsGroup to every pod securityContext
- document CI and numeric user requirements
This commit is contained in:
Noel Sabia committed 2026-11-14 05:49:06 +01:00
1 parent 5b199f8fe3
commit 23ad37699f
11 files changed
+364 -273

No files matched your search

+12 -3
View File
@@ -11,6 +11,8 @@ deploy/k8s/ web, api, ml + cloudflared Deployments and Services, Confi
deploy/examples/ example Secret shapes (placeholders only, never applied)
scripts/smoke.sh public + in-cluster smoke checks
scripts/gate1-check.sh read-only permissions/manifest/secret readiness check
scripts/check_manifests.py cluster-free manifest guardrails used by CI
.gitea/workflows/ci.yml manifest validation; no secrets, no cluster writes
k6/sse.js 120 concurrent SSE clients for 5 minutes
docs/deploy.md Gate 1 runbook and exact human checklist
docs/load-test.md load-test procedure and how to record results
@@ -50,6 +52,13 @@ hostname, and verification steps.
- Still human-only: Gitea read-only token + hello image pull, `gitea-regcred`,
Cloudflare Tunnel + DNS hostnames, and the three Secrets.
## CI
`.gitea/workflows/ci.yml` runs `make gate1-check STATIC_ONLY=1` and
`make validate`. It uses no Secrets, pushes no images, and never mutates a
cluster. If the Gitea runner is unavailable, run the same two commands
locally; `STATIC_ONLY=1` needs no kubeconfig.
## Git workflow
`main` is integration. New work happens on a `feat/<topic>` branch in its own
@@ -65,8 +74,8 @@ committed directly to `main`.
- No secrets, tokens, kubeconfig, or raw CSV in git.
- The human applies cluster mutations. `make deploy` refuses to run without
`CONFIRM=yes`.
- Every pod sets an explicit numeric `runAsUser`/`runAsGroup`: web/ml
`10001:10001`, api/cloudflared `65532:65532`. SKE rejects a non-numeric image
user under `runAsNonRoot`.
- Every pod sets explicit numeric `runAsUser`/`runAsGroup`/`fsGroup`: web/ml
`10001`, api/cloudflared `65532`. SKE rejects a non-numeric image user under
`runAsNonRoot`.
- The tunnel uses HTTP/2 (`--protocol http2`) because TCP/443 to Cloudflare is
verified and UDP/7844 is not.