15f6b11187
Turns docs/runbooks/deploy-verification.md from prose into 32 executable checks
against the live orchard9-k3sf cluster, and it found real defects on its first
run — including in the runbook it verifies.
WHY PLAYWRIGHT, HONESTLY
tidalDB serves zero HTML (no text/html, no Html(), 10 JSON routes), so this uses
Playwright in three distinct roles rather than pretending there is a UI:
* request fixture as a real HTTP client for DNS/TLS/auth/quorum/404;
* a browser for the only genuine screens in the chain, Grafana;
* a test harness for cluster-plane checks with no HTTP surface, shelling out
to kubectl and attaching the real transcript as evidence.
WHAT IT CAUGHT
* The runbook asserted the operator/data credential split was "not active yet
- requires an image roll". globalSetup read the live image and the live
secret; a probe returned data->403, admin->200. It had been enforcing the
whole time. Section 9 rewritten. (BUG-001)
* docs/ops/grafana-tidaldb.json shipped datasource uid ${DS_PROMETHEUS} - a
Grafana export-for-sharing placeholder with no __inputs block to resolve it.
Under ConfigMap provisioning every panel queried a datasource that did not
exist, so the whole board was blank. The API said "loaded" and I had only
ever checked the API. 41 refs fixed here, 58 across the fleet ConfigMap,
which was also blanking the postgres and redis dashboards. (BUG-007)
* Stat panels used calcs "lastNonNull". Grafana's reducer is "lastNotNull", so
no value was ever computed and Cluster health / Reseed pending / Indexed
vectors rendered as empty boxes. I chased panel width and then panel height
before comparing against a working stat panel elsewhere in the same Grafana.
A spelling error wearing a layout bug's clothes. (BUG-009)
* The namespace variable defaulted to All, so cluster panels silently included
tidaldb-586b544c8-vpkmw from the superseded standalone deployment. Latency
legends read "p50 p50 p50" with no way to tell the nodes apart. Both fixed.
* "5xx ratio" rendered "No data" as large green text - at a glance a healthy
value. And Fleet state gave three fields one shared green threshold, so
reseed_required=1 would have shown GREEN during the exact incident the panel
exists to surface. Split into three panels with per-field mappings.
* tidalctl cluster-status exits 2 on a FULLY CONVERGED cluster, because the
aggregated endpoint reports healthy peers as region=null applied=0
reachable=false. The runbook claimed `cluster-status && deploy` was a safe
gate; that claim came from an exit code masked by a shell pipeline. The gate
can never pass here. Documented, test pins it, engine defect recorded.
(BUG-005)
* The deployed image writes ANSI colour into container logs, which the
collector stores verbatim. Already fixed in logging.rs, not yet rolled;
pinned as a tripwire. (BUG-006)
* The runbook's own backup command sorted ALL backups by timestamp and
selected a restore-canary run: 20 items, one volume, a meaningless pass.
Now filters on the schedule label the freshness alert actually watches.
DEFECTS FOUND BY LOOKING AT THE SCREENS
Six of the first eight captures were slop and were fixed, not promoted:
230-350px of dead space; a verdict that rendered "exit code 2" in green; the
1600x1800 dashboard scaled into 16:9 until illegible (now clipped to the
evidence band using real element bounds); the dream beat whose caption described
a contradiction the image did not show (now a purpose-built capture holding the
committed doc text, the running image, and the live 403/200 side by side); and a
one-frame blink to bare background at every scene boundary, because Remotion
Sequences do not overlap and both scenes sat at opacity 0 on the boundary frame.
TRIPWIRES IN THE HONEST DIRECTION
Three tests assert what is ABSENT - zero tidaldb_http_* families, JSON_LOGS
unset, plain-text logs - and each carries the message "good news, roll the
runbook section from pending to live". The metric-absence test also asserts the
baseline family count, so "absent" cannot pass for "the scrape failed". That is
the drift that made section 9 stale in the first place.
Regression config uses workers:1 and retries:0 deliberately: a live-cluster
check that only passes on the second attempt has told you something true.
Verified: 32 passed (46.8s); 9 demo captures each asserting before photographing;
tsc clean; render 82.05s 1920x1080 h264, 0 empty frames across 10 boundaries;
every promoted image inspected individually and judged perfect; walk-the-render
ledger complete with no fails.
157 lines
6.9 KiB
JSON
157 lines
6.9 KiB
JSON
{
|
|
"schemaVersion": 1,
|
|
"buildRevision": "d21a202",
|
|
"verifiedImage": "registry.threesix.ai/tidal/server:m12-admin-gate-20260823@sha256:6e220060a342658b734d258245b20f6233d96e26415b3a44956b1c3bceebe48c",
|
|
"capturedEnvironment": "orchard9-k3sf / namespace tidaldb-cluster (live)",
|
|
"viewport": {
|
|
"width": 1600,
|
|
"height": 900
|
|
},
|
|
"captures": [
|
|
{
|
|
"id": "CAP-002-convergence",
|
|
"capabilityId": "CAP-002",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-002 every node is converged",
|
|
"file": "captures/CAP-002-convergence.png",
|
|
"expected": "Three nodes, zero lag on every shard group, no reseed pending",
|
|
"businessPurpose": "Quorum with one-node fault tolerance actually exists, rather than being assumed from pod readiness",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:69da2d8601585268be468d049afc4747aa2e6ae4c7c1f46b927e0de7ab5ca1b9",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-006-quorum-write",
|
|
"capabilityId": "CAP-006",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-005 CAP-006 the boundary refuses, then a quorum write commits",
|
|
"file": "captures/CAP-006-quorum-write.png",
|
|
"expected": "401, 401, 200, then 201 for a quorum-acked write",
|
|
"businessPurpose": "The single strongest available proof: the full stack works and the data plane is closed to strangers",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:f1fe76f19643382349006988d5bbddb68a501c1bf3037720c07e98a5a27ddfea",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-008-network-isolation",
|
|
"capabilityId": "CAP-008",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-008 the metrics port is closed to foreign pods but open to the scraper",
|
|
"file": "captures/CAP-008-network-isolation.png",
|
|
"expected": "Connection refused from a foreign namespace; hundreds of series to the scraper",
|
|
"businessPurpose": "Least-privilege network access without blinding the monitoring stack",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:247fce3324c519319176a20095a1c7a7b2b5eb5ad6745ff9046e8b6886271c6a",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-010-dashboard",
|
|
"capabilityId": "CAP-010",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-010 the operator dashboard renders live data",
|
|
"file": "captures/CAP-010-dashboard.png",
|
|
"expected": "Cluster health OK, reseed none, corpus size, and per-node latency charts \u2014 legible at delivery resolution",
|
|
"businessPurpose": "The first surface an operator opens during an incident actually shows the cluster",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 502,
|
|
"contentHash": "sha256:296570addb43426d4fbb1f8bb69b8a1fac9c691d9cdccf2e927a5db81e4407fe",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-014-authority",
|
|
"capabilityId": "CAP-014",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-014 operator authority is separate from data access",
|
|
"file": "captures/CAP-014-authority.png",
|
|
"expected": "403 for the data credential, not-403 for the admin credential",
|
|
"businessPurpose": "Blast radius of a leaked application key is bounded to data, not cluster topology",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:9897670f83c5c408b57a9c88c0097d3fcc43f983ad463be7bfbcabc49e3522b1",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-014-drift",
|
|
"capabilityId": "CAP-014",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-014 CAP-015 the harness corrected its own runbook",
|
|
"file": "captures/CAP-014-drift.png",
|
|
"expected": "The superseded claim beside the live probe that contradicts it",
|
|
"businessPurpose": "Verification that audits its own documentation instead of drifting away from it",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:7901e70f8df834a91f1399d1ad8fcf4398546bef14fa46ad23ec605e9d12a344",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-013-backup",
|
|
"capabilityId": "CAP-013",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-013 the fleet backup captured every volume",
|
|
"file": "captures/CAP-013-backup.png",
|
|
"expected": "Completed, all items, every PodVolumeBackup Completed",
|
|
"businessPurpose": "The cluster can actually be restored, and the alert is trustworthy",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:e570917de51ac352a18949117dbf6c9e990fc75127b1bc6c71d0473e2f21371f",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-015-inert",
|
|
"capabilityId": "CAP-015",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-015 what is NOT verified is stated",
|
|
"file": "captures/CAP-015-inert.png",
|
|
"expected": "Zero tidaldb_http_* families while baseline tidaldb_* families are present",
|
|
"businessPurpose": "A verification that hides its gaps cannot be trusted about the parts it claims",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:671ce44f8e3a629f88cab8f807c9389e068660f51a00e68232c9f92c87b55a76",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
},
|
|
{
|
|
"id": "CAP-012-tidalctl",
|
|
"capabilityId": "CAP-012",
|
|
"testId": "workflows/deploy-verification.demo.spec.ts :: demo capture \u2014 deploy verification :: CAP-012 tidalctl gives an operator a live view and an exit code",
|
|
"file": "captures/CAP-012-tidalctl.png",
|
|
"expected": "Leader, region table with NO REPORT markers, shard table, exit 2",
|
|
"businessPurpose": "An operator can interrogate the cluster without hand-rolling curl, and is told what the tool cannot see",
|
|
"personas": [
|
|
"cluster operator"
|
|
],
|
|
"width": 1600,
|
|
"height": 900,
|
|
"contentHash": "sha256:e13e0bfecc766d02f839334487cf0364472c43bf0f1fbe1a11159e6312a58aa6",
|
|
"audienceVerdict": "perfect",
|
|
"auditStatus": "pass"
|
|
}
|
|
]
|
|
}
|