Bump the web Deployment image from v1.3-cool to v1.4-sensing. Manifest otherwise unchanged.
PulseCast infra/QA
Namespace-only Kubernetes manifests, smoke tests, and the k6 SSE load test for
PulseCast. This repo never applies cluster changes by itself: the human runs the
commands in docs/deploy.md.
Layout
deploy/k8s/ web, api, ml + cloudflared Deployments and Services, ConfigMaps
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
docs/failure-drills.md FastAPI-down, tunnel-down, pod-restart drills
Makefile validate, build, push, deploy, smoke, load helpers
Quick start
CI checks, no cluster or kubeconfig:
make gate1-check STATIC_ONLY=1
make validate
Full deploy, human-run:
export KUBECONFIG=/path/to/fch26-onemanarmy-sa-kubeconfig.yaml # chmod 600
make gate1-check # read-only: permissions, guardrails, dry-run, Secrets
make validate # client-side dry run only, never applies
make build # all three images
make push # after docker login to Gitea
make deploy CONFIRM=yes # human only; requires the three Secrets first
make smoke # public HTTPS + API + ML health checks
make k6-build # once: pinned k6 + SSE extension
make load # 120 SSE clients for 5 minutes
make gate1-check exits 0 when ready, 1 on a hard permission/manifest failure,
and 2 when only human prerequisites (Secrets, Deployments) are pending. It
never mutates the cluster. DNS and public HTTPS are checked separately in the
runbook and by make smoke.
Read docs/deploy.md before the first deploy. It contains the Gitea token,
docker login, hello-world push, gitea-regcred, Cloudflare Tunnel, public
hostname, and verification steps.
Gate 1 status
- 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,
/tmptmpfs, numeric UID). There is no Dockerfile blocker. - Gitea pull is proven:
gitea-regcredexists and the hello pod pulled fromgit.noelsabia.dev/noel/hello:gate1; the Service returned HTTP 200. - Tunnel
pulsecast-gate1is active withpulseandapi-pulseroutes.pulseserves the v1.1 Nuxt app;/stageand/livereturn 200, and/controlrequires auth. The API hostname isapi-pulse.noelsabia.devbecause Universal SSL only covers*.noelsabia.dev. - v1.1 is deployed: web/api/ml
:v1.1, cloudflared2026.11.0, all four Deployments Ready. - The v1.1 120-VU Cloudflare run passed: 120/120 connections, 0 errors, p95
event 331 ms, p95 scenario 646 ms, presenter 49.60 ms. The v1.0 baseline is
retained for comparison in
docs/load-test.md. - The ML-down/API-restart failure drill passed; details are in
docs/failure-drills.md. - 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 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
main is integration. New work happens on a feat/<topic> branch in its own
worktree. Before every push: git fetch origin && git merge origin/main.
Never force-push main. The initial scaffold is the one bootstrap exception
committed directly to main.
Safety rules
- No Ingress, cert-manager, external-dns, Jobs, CronJobs, CRDs, Roles, RoleBindings, NetworkPolicies, or any cluster-scoped resource.
- Exposure only through the
cloudflaredDeployment. - No secrets, tokens, kubeconfig, or raw CSV in git.
- The human applies cluster mutations.
make deployrefuses to run withoutCONFIRM=yes. - Every pod sets explicit numeric
runAsUser/runAsGroup/fsGroup: web/ml10001, api/cloudflared65532. SKE rejects a non-numeric image user underrunAsNonRoot. - The tunnel uses HTTP/2 (
--protocol http2) because TCP/443 to Cloudflare is verified and UDP/7844 is not.