unkin-agent
abf73bb5bf
## 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. Reviewed-on: #444 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
17 lines
341 B
YAML
17 lines
341 B
YAML
---
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
resources:
|
|
- cnpg_cluster.yaml
|
|
- cnpg_backup.yaml
|
|
- vaultstaticsecret.yaml
|
|
- tiers-configmap.yaml
|
|
- oauth2-proxy-configmap.yaml
|
|
- oauth2-proxy-deployment.yaml
|
|
- api-deployment.yaml
|
|
- ui-deployment.yaml
|
|
- services.yaml
|
|
- gateway.yaml
|
|
- httproute.yaml
|