unkin/argocd-apps
3
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

arrproxy: v0.6.0 self-migrating, drop external migrate Job #444

Merged
benvin merged 1 commits from benvin/arrproxy-0.6.0-selfmigrate into main 2026-08-30 15:30:44 +10:00
Conversation 0 Commits 1 Files Changed 5
+5 -143
unkin-agent commented 2026-08-30 15:15:26 +10:00
Member
Copy Link
Copy Source

Why

arrproxy v0.6.0 applies its own schema at startup under a Postgres advisory lock and holds /readyz until the schema is current, so every replica is safe to roll without an external gate. The wave-1 psql arrproxy-migrate Job and its SQL ConfigMap now only re-run idempotent statements the app already owns — dead weight, a second source of truth for the schema, and a standing drift trap whenever the app's embedded migrations move ahead of the manifests.

How

  • Bump arrproxy-api and arrproxy-ui to v0.6.0.
  • Delete migrate-job.yaml and migrations-configmap.yaml and drop both from the arrproxy kustomization.
  • Keep the wave-0/wave-2 split: wave 2 still orders the api behind the wave-0 CNPG Cluster and VSO-synced Secrets, which is independent of the migrate Job; the stale "serve only after the wave-1 migrate Job" comment is corrected.
  • Rendered diff vs main is exactly the two image bumps plus the arrproxy-migrate Job and arrproxy-migrations ConfigMap disappearing; kustomize build --enable-helm apps/overlays/au-syd1/arrstack and pre-commit both clean.
## Why arrproxy v0.6.0 applies its own schema at startup under a Postgres advisory lock and holds `/readyz` until the schema is current, so every replica is safe to roll without an external gate. The wave-1 psql `arrproxy-migrate` Job and its SQL ConfigMap now only re-run idempotent statements the app already owns — dead weight, a second source of truth for the schema, and a standing drift trap whenever the app's embedded migrations move ahead of the manifests. ## How - Bump `arrproxy-api` and `arrproxy-ui` to `v0.6.0`. - Delete `migrate-job.yaml` and `migrations-configmap.yaml` and drop both from the arrproxy kustomization. - Keep the wave-0/wave-2 split: wave 2 still orders the api behind the wave-0 CNPG Cluster and VSO-synced Secrets, which is independent of the migrate Job; the stale "serve only after the wave-1 migrate Job" comment is corrected. - Rendered diff vs `main` is exactly the two image bumps plus the `arrproxy-migrate` Job and `arrproxy-migrations` ConfigMap disappearing; `kustomize build --enable-helm apps/overlays/au-syd1/arrstack` and pre-commit both clean.
unkin-agent added 1 commit 2026-08-30 15:15:26 +10:00
arrproxy: v0.6.0 self-migrating, drop external migrate Job
ci/woodpecker/pr/vector-test Pipeline was successful
Details
ci/woodpecker/pr/pre-commit Pipeline was successful
Details
ci/woodpecker/pr/kubeconform Pipeline was successful
Details
d528dffb5b 
Bump arrproxy-api and arrproxy-ui to v0.6.0 and remove the psql migrate Job
plus its migrations ConfigMap. v0.6.0 applies its own schema at startup under
a Postgres advisory lock and holds /readyz until it is current, so the
external hook is dead weight and a drift trap.
benvin merged commit abf73bb5bf into main 2026-08-30 15:30:44 +10:00
benvin deleted branch benvin/arrproxy-0.6.0-selfmigrate 2026-08-30 15:30:44 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkin-agent (Unkin Agent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#444
Delete Branch "benvin/arrproxy-0.6.0-selfmigrate"

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?