ci: run manifest checks on the Gitea runner
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:
1 parent
bd3176bef0
commit
e8e048866c
10 files changed
+102
-104
No files matched your search
+9
-8
@@ -15,13 +15,14 @@ Build the pinned binary once:
|
||||
|
||||
```bash
|
||||
make k6-build # creates k6/k6-sse (git-ignored)
|
||||
./k6/k6-sse version # expect k6 v2.0.0 + xk6-sse v0.2.0
|
||||
./k6/k6-sse version # expect k6 v2.0.0 + the current xk6-sse
|
||||
```
|
||||
|
||||
The build pins **k6 v2.0.0**. On k6 v2.4.0 the same `xk6-sse` v0.2.0 build
|
||||
fails at runtime with `TypeError: Object has no member 'on'` (the extension's
|
||||
client methods are not exposed); v2.0.0 was verified locally on 2026-11-14. If
|
||||
you bump `K6_BUILD_VERSION`, rerun the script against a test stream first.
|
||||
The build pins **k6 v2.0.0**; `xk6-sse` v0.2.0 is the version used for the
|
||||
recorded runs. On k6 v2.4.0 that extension build fails at runtime with
|
||||
`TypeError: Object has no member 'on'` (the client methods are not exposed);
|
||||
v2.0.0 was verified locally on 2026-11-14. If you bump `K6_BUILD_VERSION`,
|
||||
rerun the script against a test stream first.
|
||||
|
||||
`make load` uses, in order: `K6` if set, `k6/k6-sse`, then `k6` on `PATH`.
|
||||
A stock `grafana/k6` image is **not** a fallback: it lacks the SSE extension.
|
||||
@@ -79,9 +80,9 @@ A stock `grafana/k6` image is **not** a fallback: it lacks the SSE extension.
|
||||
The script was validated locally on 2026-11-14 with the pinned k6 v2.0.0 build
|
||||
against a mock SSE stream and the real v1.1 API image (3 VUs, 1 heartbeat
|
||||
each): connections opened and closed cleanly, open success 100%, presenter
|
||||
POST 200, and scenario latency sampled. The real 120-client run still requires
|
||||
the deployed API, because localhost results say nothing about Cloudflare
|
||||
buffering or SKE scheduling.
|
||||
POST 200, and scenario latency sampled. Run the 120-client test against the
|
||||
deployed API; localhost says nothing about Cloudflare buffering or SKE
|
||||
scheduling.
|
||||
|
||||
## Pass criteria
|
||||
|
||||
|
||||
Reference in new issue
Block a user