Validation: Kustomize overlay (issue #3)
Verdict: PARTIAL
Ticket
forgejo_admin/twitch-2k-wager#3 — Kustomize overlay (pal-e-deployments)
Board item #788 on board-twitch-2k-wager
Environment
Production cluster (archbox), namespace: playme2k, ArgoCD application: playme2k
Checks
| # | Criterion | How Verified | Result | Evidence |
|---|---|---|---|---|
| 1 | Kustomize overlay exists in pal-e-deployments | git show origin/main:overlays/twitch-2k-wager/prod/kustomization.yaml | PASS | Full kustomization.yaml present on remote main. Contains deployment patches, service patches, Harbor image reference (harbor.tail5b443a.ts.net/playme2k/app), and tag 82768f26... |
| 2 | ArgoCD sync status is Synced | kubectl get application playme2k -n argocd -o jsonpath='{.status.sync.status}' | FAIL | Status: OutOfSync. ArgoCD is not in a clean synced state. |
| 3 | ArgoCD health status is Healthy | kubectl get application playme2k -n argocd -o jsonpath='{.status.health.status}' | FAIL | Status: Progressing. Deployment twitch-2k-wager has 0/1 available replicas due to ImagePullBackOff. |
| 4 | Target pods running new image | kubectl get deployment -n playme2k -o wide | FAIL | twitch-2k-wager deployment READY 0/1. Image: harbor.tail5b443a.ts.net/playme2k/app:82768f26... — correct tag but pod cannot pull (missing Harbor project + harbor-creds secret). |
Regression Check
No regression to existing overlays. Only new overlay affected. Dev overlay (playme2k-dev) is healthy and unrelated to this prod overlay.
Discovered Issues
- Overlay kustomization is correct and tag was updated by CI, but the deployment cannot converge because upstream blockers (Harbor project missing, harbor-creds secret missing) prevent image pull. These are issue #1 scope, not #3 scope.
- The overlay itself is structurally correct — once Harbor/creds are fixed, ArgoCD should sync to Healthy.