Reviewed screenshot gallery

The canonical manifest contains 29 reviewed captures and five detail companions, captured during the October 2–3, 2026 campaign. Filters narrow this recorded dataset; they do not query a live cluster. Every card preserves the original image hash, capture time, stated source identity, observed window, and exact visible proof.

What an image establishes

A dashboard can illustrate a failure or recovery window. It cannot establish a gate verdict, exact candidate binding, useful traffic continuity, or completed cleanup by itself. A configuration screenshot establishes what was visible when captured. Missing metadata remains “Not recorded”; no image receives a passing score from its color or title.

The display image is an optimized WebP derivative. Open original PNG exposes the reviewed bytes without modification. Select a thumbnail to enlarge it; Escape closes the viewer and returns focus to the thumbnail. Without JavaScript every original link and evidence card remains available.

GitHubstatic

01 · Release title, latest status, tag, commit, and changelog link

configuration snapshot · result not inferred from image

Captured (UTC): 2026-10-02T10:15:13Z
Observed window: Not recorded
Source identity: v1.0.0 / 3b70835335462f1b6f9b1dd17ab20d1108724f89

Identity and provenance

Freight: Not recorded
OCI identity: Not recorded
Rendered revision: Not recorded
AnalysisRun: Not recorded
Original SHA-256: 41a68298f38830240e5408cfd8ec6e3e4e3c11b4a375b77cf1b2cda06fbf407b
Display derivative: 720px WebP; a display copy of the reviewed PNG.

Reviewed screenshot gallery

What an image establishes

01 · Release title, latest status, tag, commit, and changelog link

02 · Four successful validation and image-publication workflows for release commit 3b70835

03 · Successful OIDC authentication, immutable build/push, Cosign sign/verify, identity record, and artifact upload

04 · Healthy resilience-gate Standard zonal cluster in us-central1-a, two nodes, version 1.35.8-gke.1225000

04b · GKE Workload Identity enabled with namespace shivam-serverless.svc.id.goog

05 · Healthy general-pool with two e2-standard-4 nodes in us-central1-a

05b · Auto-upgrade and auto-repair enabled; auto-upgrade active

06 · Three release images, immutable digests, and full release-SHA tags

07 · Active GitHub OIDC provider restricted to this repository, main, push, and workflow dispatch

08 · Eight platform/environment Applications, all Healthy and Synced

09 · Application visibly Healthy and Synced to env/staging revision 64d2dde; all 21 displayed resources report synced/healthy and current deployment, PostgreSQL, Redis, and ExternalSecret branches are green

10 · Complete Warehouse-to-dev-to-staging-to-prod graph; all three Stages show green health and current Freight hoping-warthog; selected Freight timeline card shows source 0a98c0 and image sha-3b…f89 artifacts

11 · Exact AnalysisRun title, green Analysis passed summary, and green chaos-verdict plus readiness; selected Freight history card shows hoping-warthog. Kargo's table value 853b0a1 is the verification-history ID, live-mapped to this Freight

12 · Exact historical AnalysisRun visibly failed while the staging Stage retained green health indicators

12b · Exact AnalysisRun visibly failed: readiness successful, chaos-verdict failed, and failure-limit message shown

13 · Kargo v1.3.0 visibly disables intentional-liger for prod while staging-verified Freight remains selectable; full pipeline visible

14 · Branch env/staging, repository path, config and external-secret checksum annotations, hardened pod settings, and digest-qualified application image are legible; companion 14b supplies the render-commit linkage

14b · Repository, branch env/staging, generated Deployment identity, Kargo render commit message, and short revision 64d2dde are visible; paired with Screenshot 14 for checksums and full immutable digest

15 · Exact cluster, namespace, Job, Pod, AnalysisRun, UTC window, /scripts/loadgen.js, three max VUs, one iteration/s, ten-minute bound, and initial progress

16 · Aggregate k6 counts and expected fault-window errors, final interrupted lifecycle, independent GATE VERDICT: PASS, cleanup deadline, and exact load Job cleanup

17 · Dashboard identity, staging selector, absolute UTC window, PASS region, traffic and bounded 5xx, route p95, and distinct PostgreSQL/Redis/signer outage-and-recovery traces

17b · Four application restart series remain zero; scoped /shorten 503 degradation; annotation posted; explicit GATE VERDICT: PASS; verified cleanup; concise bounded-load excerpt

18 · PostgreSQL Ready state falls from 1 to 0 and returns to 1 while non-probe traffic continues; the associated bounded 5xx interval and route p95 remain visible

19 · Redis Ready state alone falls from 1 to 0 and returns to 1; redirect p95 rises during database fallback then recovers while traffic continues and 5xx remains zero

20 · Signer Ready state falls from 1 to 0 and returns to 1 while PostgreSQL and Redis remain ready; application traffic recovers and 5xx remains zero

21 · Annotation popup visibly identifies 2026-10-02T05:21:20Z–05:29:50Z, chaos-gate PASS (chaos-gate-fkftr), and tags chaos-gate / verdict:pass over the correlated traffic, 5xx, latency, and fault-recovery panels

22 · Annotation popup visibly identifies 2026-10-02T03:26:25Z–03:34:55Z, chaos-gate FAIL — failed: postgres,redis (chaos-gate-n5x4w), and tags chaos-gate / verdict:fail over the correlated historical panels

23 · Populated paid HTTP/payment-decision series, green 100% settled-payment success, green zero replay attempts, successful facilitator throughput and latency, signer success/latency, and all three wallet indexes at allowance/budget readiness 1

24 · Ordered POST 402 challenge, POST 201 settlement, GET 302 redirect, and POST 409 replay rejection; helper validates 402 -> 201 -> 302 -> 409 [PASS] before rendering

25 · Signer throughput is successful, p50/p95 latency is populated, and all three wallet_index series remain at 1 for Permit2 allowance and bounded budget readiness

26 · Zero active Promotions, AnalysisRuns, Lease, Workflows, WorkflowNodes, PodChaos, load Jobs, gate Jobs, and prod CronJobs; staging source CronJob suspended; application 2/2, signer/PostgreSQL/Redis 1/1; overall PASS

27 · Nine ExternalSecrets use the expected store and report True / SecretSynced

28 · All populated target pools green, including CoreDNS 2/2, application environments, signer, kube-state-metrics, node-exporter, and Prometheus

29 · Application visibly Healthy and Synced to env/prod (7d334d5); all 21 resources report synced/healthy; three application Pods, PostgreSQL, and Redis show green Running/Ready state

Keep the records distinct

Canonical source