feat: prepare v1.1 deploy and presenter load test
infra-ci / manifests (push) Failing after 4s
infra-ci / manifests (pull_request) Failing after 3s

- build and push v1.1 images from the service main worktrees
- switch manifests to :v1.1; add web control Secret refs
- configure API BOOTSTRAP_REFRESH=60s and remove unused DATA_DIR
- add k6 presenter scenario with a mid-run control POST
- require control credentials in make load; update runbook and drills
This commit is contained in:
Noel Sabia committed 2026-11-14 08:00:58 +01:00
1 parent 40bc8e47d0
commit b98a1bab42
12 files changed
+264 -117

No files matched your search

+12 -8
View File
@@ -45,17 +45,21 @@ hostname, and verification steps.
## Gate 1 status
- Manifests validate read-only; `make gate1-check` is green except for pending
human prerequisites.
- All three images build and pass local manifest-equivalent runtime checks
- 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.
- 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
`git.noelsabia.dev/noel/hello:gate1`; the Service returned HTTP 200.
- Tunnel `pulsecast-gate1` is active with `pulse` and `api-pulse` routes;
`https://pulse.noelsabia.dev` returns 200 from hello with valid TLS. The API
hostname is `api-pulse.noelsabia.dev` because Universal SSL only covers
`*.noelsabia.dev`.
- Still needed: `control-auth` Secret, image push, deploy, and public smoke.
- Tunnel `pulsecast-gate1` is active with `pulse` and `api-pulse` routes.
`pulse` still points at the temporary hello Service until the v1.1 cutover.
The API hostname is `api-pulse.noelsabia.dev` because Universal SSL only
covers `*.noelsabia.dev`.
- v1.1 images are built from the service `main` worktrees, locally checked,
and pushed. The cluster still runs the previous v1.0 images until this branch
is reviewed/merged and explicitly applied.
- The v1.1 branch adds web control credentials, API bootstrap config, and the
k6 presenter scenario; load-test results are recorded after the approved run.
## CI