ci: run manifest checks on the Gitea runner
infra-ci / manifests (push) Successful in 8s
infra-ci / manifests (pull_request) Successful in 8s

The node:20-bookworm runner has python3 but no pip, so the PyYAML install failed before any check ran. Install python3-yaml with apt instead, remove the duplicate cluster-only kubectl step, and keep the two cluster-free Make targets.

Also remove the stale v1.0/pending-review claims, drop the old api.pulse hostname, and move the deploy status below the runbook.
This commit is contained in:
Noel Sabia committed 2026-11-14 09:13:27 +01:00
1 parent bd3176bef0
commit e8e048866c
10 files changed
+102 -104

No files matched your search

+16 -7
View File
@@ -22,6 +22,15 @@ Makefile validate, build, push, deploy, smoke, load helpers
## Quick start
CI checks, no cluster or kubeconfig:
```bash
make gate1-check STATIC_ONLY=1
make validate
```
Full deploy, human-run:
```bash
export KUBECONFIG=/path/to/fch26-onemanarmy-sa-kubeconfig.yaml # chmod 600
make gate1-check # read-only: permissions, guardrails, dry-run, Secrets
@@ -45,8 +54,8 @@ hostname, and verification steps.
## Gate 1 status
- Static `make gate1-check STATIC_ONLY=1`/CI passes. The live check correctly
flags the cluster's v1.0 images until the reviewed v1.1 branch is applied.
- CI runs the cluster-free checks (`STATIC_ONLY=1`, `make validate`) and passes;
the live check is the human-run Gate 1 check with a kubeconfig.
- All three v1.1 images build and pass local manifest-equivalent runtime checks
(read-only root, `/tmp` tmpfs, numeric UID). There is no Dockerfile blocker.
- Gitea pull is proven: `gitea-regcred` exists and the hello pod pulled from
@@ -63,15 +72,15 @@ hostname, and verification steps.
retained for comparison in `docs/load-test.md`.
- The ML-down/API-restart failure drill passed; details are in
`docs/failure-drills.md`.
- The results documentation still needs a new PR review/merge; the v1.1
runtime code is already merged in `main`.
- The v1.1 results are merged in `main`; this branch only updates CI and docs.
## 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.
`make validate` on a `node:20-bookworm` runner. It installs `python3-yaml`,
uses no Secrets, pushes no images, and never touches a cluster. Run the same
two commands locally; both work without a kubeconfig but need PyYAML
(`python3-yaml`).
## Git workflow