Fix CI registry URL to use cluster-internal Harbor address #18

New issue

Closed

opened 2026-05-25 03:04:28 +00:00 by ldraney · 0 comments

ldraney commented

2026-05-25 03:04:28 +00:00

Owner

Type

Feature

Lineage

Standalone -- discovered during observability gap audit reviewing CI pipeline config.

Repo

ldraney/landscaping-assistant

User Story

As a developer
I want the CI build step to push images via the internal Harbor address
So that builds are not subject to transient Tailscale/external network failures

Context

The .woodpecker.yaml kaniko build-and-push step uses registry: harbor.tail5b443a.ts.net (external Tailscale URL). Since Woodpecker runs inside k3s, it can reach Harbor directly via harbor-core.harbor.svc.cluster.local. Using the external URL introduces unnecessary dependency on Tailscale connectivity and causes transient build failures. The kustomize overlay image references should continue using the external URL since ArgoCD pulls from outside the cluster.

File Targets

Files the agent should modify or create:

.woodpecker.yaml -- change registry from harbor.tail5b443a.ts.net to harbor-core.harbor.svc.cluster.local in the build-and-push step

Files the agent should NOT touch:

overlays/landscaping-assistant/prod/kustomization.yaml (in pal-e-deployments) -- image references there use external URL correctly for ArgoCD
Clone step and test steps in .woodpecker.yaml -- unrelated

Acceptance Criteria

registry field in kaniko step changed to harbor-core.harbor.svc.cluster.local
repo field uses correct path format for internal registry
A push to a feature branch triggers a successful pipeline build-and-push
Image is accessible via external Harbor URL after push (Harbor serves both)

Test Expectations

Integration: push a commit to a feature branch and verify the pipeline build-and-push step succeeds
Manual: verify image appears in Harbor UI under landscaping-assistant/app
Run command: woodpecker-cli pipeline last ldraney/landscaping-assistant

Constraints

Only change the registry push target, not the image pull references in kustomize
Verify kaniko plugin handles harbor-core.harbor.svc.cluster.local on port 80

Checklist

PR opened
Pipeline passes
No unrelated changes

project-landscaping-assistant -- project this affects

### Type Feature ### Lineage Standalone -- discovered during observability gap audit reviewing CI pipeline config. ### Repo `ldraney/landscaping-assistant` ### User Story As a developer I want the CI build step to push images via the internal Harbor address So that builds are not subject to transient Tailscale/external network failures ### Context The `.woodpecker.yaml` kaniko build-and-push step uses `registry: harbor.tail5b443a.ts.net` (external Tailscale URL). Since Woodpecker runs inside k3s, it can reach Harbor directly via `harbor-core.harbor.svc.cluster.local`. Using the external URL introduces unnecessary dependency on Tailscale connectivity and causes transient build failures. The kustomize overlay image references should continue using the external URL since ArgoCD pulls from outside the cluster. ### File Targets Files the agent should modify or create: - `.woodpecker.yaml` -- change `registry` from `harbor.tail5b443a.ts.net` to `harbor-core.harbor.svc.cluster.local` in the build-and-push step Files the agent should NOT touch: - `overlays/landscaping-assistant/prod/kustomization.yaml` (in pal-e-deployments) -- image references there use external URL correctly for ArgoCD - Clone step and test steps in `.woodpecker.yaml` -- unrelated ### Acceptance Criteria - [ ] `registry` field in kaniko step changed to `harbor-core.harbor.svc.cluster.local` - [ ] `repo` field uses correct path format for internal registry - [ ] A push to a feature branch triggers a successful pipeline build-and-push - [ ] Image is accessible via external Harbor URL after push (Harbor serves both) ### Test Expectations - [ ] Integration: push a commit to a feature branch and verify the pipeline build-and-push step succeeds - [ ] Manual: verify image appears in Harbor UI under landscaping-assistant/app - Run command: `woodpecker-cli pipeline last ldraney/landscaping-assistant` ### Constraints - Only change the registry push target, not the image pull references in kustomize - Verify kaniko plugin handles `harbor-core.harbor.svc.cluster.local` on port 80 ### Checklist - [ ] PR opened - [ ] Pipeline passes - [ ] No unrelated changes ### Related - `project-landscaping-assistant` -- project this affects