Remove ArgoCD Image Updater ghost override blocking deployment #89

New issue

Closed

opened 2026-03-06 21:20:47 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-06 21:20:47 +00:00

Contributor

Plan

plan-2026-02-26-tf-modularize-postgres -- Phase 5 deployment blocker

Repo

forgejo_admin/pal-e-docs

User Story

As a platform operator
I want ArgoCD to deploy the image tag specified in deployment.yaml
So that merged code actually reaches production

Context

The ArgoCD Image Updater previously wrote a .argocd-source-pal-e-docs.yaml file into k8s/. This kustomize override pins the image to e065419... (an old SHA). Even though the Image Updater is broken, the override file persists and takes priority over k8s/deployment.yaml.

ArgoCD reports "Synced" but the pod runs the old image. Phase 5 tsvector search (PR #84) is merged but not deployed because of this ghost file.

The file is NOT tracked in Git — it exists only in the ArgoCD repo cache. We need to either:

Add it to Git as a deletion (commit a .gitignore entry or remove it from ArgoCD's source)
Or remove the Image Updater annotations from the ArgoCD Application

File Targets

k8s/.argocd-source-pal-e-docs.yaml — delete this file and commit the deletion
Consider adding k8s/.argocd-source-* to .gitignore to prevent future ghost overrides

Acceptance Criteria

.argocd-source-pal-e-docs.yaml is gone (either deleted from ArgoCD's view or overridden)
ArgoCD deploys harbor.tail5b443a.ts.net/pal-e-docs/api:c85a39da313a80ebde109895fd281cd7ff7c9275
Pod restarts with new image
GET /notes/search?q=postgres returns results

Test Expectations

kubectl get deployment pal-e-docs -n pal-e-docs -o jsonpath='{.spec.template.spec.containers[0].image}' shows new SHA
Search endpoint responds

Constraints

The file is NOT in Git. It was written by the Image Updater directly into ArgoCD's source. You may need to either: (a) track it in Git and commit its deletion, or (b) use kubectl to patch the ArgoCD Application to remove the image-updater annotations, or (c) delete the file from wherever ArgoCD caches the repo and force a hard refresh.
Simplest approach: remove the image-updater annotations from the ArgoCD Application spec so it stops honoring the override file.

Checklist

PR opened or kubectl fix applied
Deployment verified

pal-e-docs project
phase-postgres-5-fulltext-search
bug-argocd-image-updater-ghost-override

### Plan `plan-2026-02-26-tf-modularize-postgres` -- Phase 5 deployment blocker ### Repo `forgejo_admin/pal-e-docs` ### User Story As a platform operator I want ArgoCD to deploy the image tag specified in deployment.yaml So that merged code actually reaches production ### Context The ArgoCD Image Updater previously wrote a `.argocd-source-pal-e-docs.yaml` file into `k8s/`. This kustomize override pins the image to `e065419...` (an old SHA). Even though the Image Updater is broken, the override file persists and takes priority over `k8s/deployment.yaml`. ArgoCD reports "Synced" but the pod runs the old image. Phase 5 tsvector search (PR #84) is merged but not deployed because of this ghost file. The file is NOT tracked in Git — it exists only in the ArgoCD repo cache. We need to either: 1. Add it to Git as a deletion (commit a `.gitignore` entry or remove it from ArgoCD's source) 2. Or remove the Image Updater annotations from the ArgoCD Application ### File Targets - `k8s/.argocd-source-pal-e-docs.yaml` — delete this file and commit the deletion - Consider adding `k8s/.argocd-source-*` to `.gitignore` to prevent future ghost overrides ### Acceptance Criteria - [ ] `.argocd-source-pal-e-docs.yaml` is gone (either deleted from ArgoCD's view or overridden) - [ ] ArgoCD deploys `harbor.tail5b443a.ts.net/pal-e-docs/api:c85a39da313a80ebde109895fd281cd7ff7c9275` - [ ] Pod restarts with new image - [ ] `GET /notes/search?q=postgres` returns results ### Test Expectations - [ ] `kubectl get deployment pal-e-docs -n pal-e-docs -o jsonpath='{.spec.template.spec.containers[0].image}'` shows new SHA - [ ] Search endpoint responds ### Constraints - The file is NOT in Git. It was written by the Image Updater directly into ArgoCD's source. You may need to either: (a) track it in Git and commit its deletion, or (b) use `kubectl` to patch the ArgoCD Application to remove the image-updater annotations, or (c) delete the file from wherever ArgoCD caches the repo and force a hard refresh. - Simplest approach: remove the image-updater annotations from the ArgoCD Application spec so it stops honoring the override file. ### Checklist - [ ] PR opened or kubectl fix applied - [ ] Deployment verified ### Related - `pal-e-docs` project - `phase-postgres-5-fulltext-search` - `bug-argocd-image-updater-ghost-override`