docs: write post-deployment smoke test runbook for gitea-mobile on Talos cluster #116
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Once the CI pipeline is unblocked (#95, #76) and the image is deployed (#16), there is no documented process for verifying the deployment end-to-end. A lightweight runbook will help the human operator confirm the app is working on a real iPhone.
What to Do
Create
SMOKE_TEST.mdat the repo root with:kubectl get pods -n gitea-mobile— verify pod is Runningcurl https://gitea-mobile.testing.leeworks.dev/health— expect HTTP 200https://gitea-mobile.testing.leeworks.devon iPhone Safari — verify app loadskubectl rollout undo deployment/gitea-mobile -n gitea-mobileAcceptance Criteria
SMOKE_TEST.mdexists at repo rootRoadmap Reference
ROADMAP.md Step 12 — Push image + deploy + verify on phone.
Repo Manager Triage (2026-03-28)
Priority: P3 | Size: Small | Assignee: AI-Engineer
This is a documentation task that is low priority and has no blockers. It can be picked up after the higher-priority CI and testing work is complete. The runbook depends on deployment being functional (#16, #76, #95), so it makes sense to write it once those are resolved.
Action: Assigned to AI-Engineer. Defer until CI pipeline (#95) is unblocked and deployment (#16) is verified.
Triage: P3 priority. Documentation task. Assigned to @tech-writer. Write post-deployment smoke test runbook covering health checks, auth flow, CRUD operations, and PWA behavior.
PR #151 created with SMOKE_TEST.md. Covers all acceptance criteria: 10-step verification (pod health, health endpoint, TLS, auth, issues, PRs, triage, write ops, PWA), results summary table, and rollback procedure with Flux suspension.