Bug: CI pushes image to wrong Harbor project (westside-app vs westsidekingsandqueens) #100

New issue

Closed

opened 2026-03-27 04:15:50 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-27 04:15:50 +00:00

Owner

Type

Bug

Lineage

Discovered during westside-app deployment session. CI pipeline builds successfully but image lands in wrong Harbor project, so ArgoCD can't pull it.

Repo

forgejo_admin/westside-app

What Broke

CI pipeline pushes the Docker image to harbor.harbor.svc.cluster.local/westside-app/app:${SHA} but the kustomize overlay in pal-e-deployments pulls from harbor.tail5b443a.ts.net/westsidekingsandqueens/app:${TAG}. The image goes to the wrong Harbor project and the deployment can't find it.

Repro Steps

Merge any PR to westside-app main
CI pipeline runs — tests pass, Kaniko builds and pushes to westside-app/app
ArgoCD tries to deploy using westsidekingsandqueens/app image
Pull fails — image doesn't exist in that project

Expected Behavior

CI should push to westsidekingsandqueens/app to match the kustomize overlay, OR the overlay should be updated to pull from westside-app/app. Either way, push and pull must use the same Harbor project.

Environment

CI: .woodpecker.yaml line ~38: repo: westside-app/app
Deploy: pal-e-deployments/overlays/westsidekingsandqueens/prod/kustomization.yaml line 64: newName: harbor.tail5b443a.ts.net/westsidekingsandqueens/app
Harbor projects: need to verify which project(s) exist

Acceptance Criteria

CI push target and kustomize pull source use the same Harbor project
Image pushed by CI is pullable by the deployment
ArgoCD sync succeeds for westsidekingsandqueens app after next merge

#184 (pal-e-platform) — parent incident
project-westside-basketball

### Type Bug ### Lineage Discovered during westside-app deployment session. CI pipeline builds successfully but image lands in wrong Harbor project, so ArgoCD can't pull it. ### Repo `forgejo_admin/westside-app` ### What Broke CI pipeline pushes the Docker image to `harbor.harbor.svc.cluster.local/westside-app/app:${SHA}` but the kustomize overlay in pal-e-deployments pulls from `harbor.tail5b443a.ts.net/westsidekingsandqueens/app:${TAG}`. The image goes to the wrong Harbor project and the deployment can't find it. ### Repro Steps 1. Merge any PR to westside-app main 2. CI pipeline runs — tests pass, Kaniko builds and pushes to `westside-app/app` 3. ArgoCD tries to deploy using `westsidekingsandqueens/app` image 4. Pull fails — image doesn't exist in that project ### Expected Behavior CI should push to `westsidekingsandqueens/app` to match the kustomize overlay, OR the overlay should be updated to pull from `westside-app/app`. Either way, push and pull must use the same Harbor project. ### Environment - CI: `.woodpecker.yaml` line ~38: `repo: westside-app/app` - Deploy: `pal-e-deployments/overlays/westsidekingsandqueens/prod/kustomization.yaml` line 64: `newName: harbor.tail5b443a.ts.net/westsidekingsandqueens/app` - Harbor projects: need to verify which project(s) exist ### Acceptance Criteria - [ ] CI push target and kustomize pull source use the same Harbor project - [ ] Image pushed by CI is pullable by the deployment - [ ] ArgoCD sync succeeds for westsidekingsandqueens app after next merge ### Related - #184 (pal-e-platform) — parent incident - `project-westside-basketball`