[Phase 0] Validate full-stack deployment readiness for VIN Decoder after operator secrets are in place #157
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?
Roadmap reference
Phase 0 / Phase 3 — VIN Decoder. This is the VIN Decoder analogue of issue #66 (full-stack validation for the original 3 APIs).
Trigger
This issue becomes actionable once ALL of the following operator tasks are done:
gitea-registryimagePullSecret invin-decodernamespace (issue #127)GITEA_TOKENActions secret inleeworks-agents/vin-decoderrepo (issue #126)rapidapi-proxy-secretinvin-decodernamespace (issue #128)Validation checklist
kubectl get pods -n vin-decoder→ pod Running (no ImagePullBackOff)curl -s https://vin.leeworks.dev/v1/health→ HTTP 200 withstatus: okcurl -s -H 'X-RapidAPI-Proxy-Secret: PLACEHOLDER' https://vin.leeworks.dev/v1/decode?vin=1HGCM82633A004352→ HTTP 200 with decoded fieldscurl -s https://vin.leeworks.dev/v1/decode?vin=1HGCM82633A004352(no header) → HTTP 403flux get kustomizations vin-decoder→READY=Trueapi_requests_totalandapi_response_duration_secondsmetrics for vin-decoderAcceptance criteria
Estimated effort: 1 hour
Dependencies
@devops / @operator-required — 2026-06-01 triage. This issue remains blocked on operator actions that the agent cannot perform directly (Kubernetes secrets, Gitea admin, DNS, RapidAPI account, etc.). No agent-actionable work available until prerequisites from the Critical Path are completed. See STATUS.md Current Blockers section for the ordered dependency list.
[@qa-engineer triage — 2026-06-01]
🚫 Still blocked — depends on all of the following:
Agent-side code (#120, #121) is complete. All remaining blockers are manual operator actions (secrets, DNS, Talos wiring).
[@qa-engineer triage — 2026-06-01 second pass]
✅ STATUS.md updated — PR #162 merged. VIN Decoder Code column is now
[x].Remaining blockers preventing full-stack validation:
This issue remains open; it becomes actionable once the operator completes the manual prerequisites above.