GitOps-safe: generateSecrets, and Argo CD hook order (K-C14) #40

Merged
jcoffey-dev merged 1 commits from feat/gitops-safe into main 2026-11-20 08:16:38 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 7586a3faee GitOps-safe: generateSecrets, and Argo CD hook order (K-C14)
ci / chart (pull_request) Successful in 39s
lab / e2e the lab on GitHub passed
Argo CD and helm template | kubectl apply render without the cluster, so
lookup returns nothing and the webmail's and metrics Secrets were made new
on every sync: never Synced, and every webmail user signed out.
generateSecrets: false (default true) makes the chart refuse to render
until webmail.existingSecret and server.metrics.prometheus.existingSecret
are named.

Argo runs pre-install and pre-upgrade hooks as PreSync on every sync, so
the seed ran every time and, on a first sync, at the same weight as the
upgrade Job. Every hook now carries Argo's own hook, sync-wave and delete
policy annotations beside Helm's: hook NetworkPolicies (-30), the upgrade
(-25 to -20), then the seed (-15, -10). Upgrade first matters: --seed
upgrades the store's layout before it seeds, which would skip the
acknowledgement and the stop. On a new store --upgrade-plan exits 0 and
writes no defaults, so the seed after it still sees a new store. The
egress check is PostSync. Helm's own weights are unchanged.

The release's rendered manifests (defaults) contain no Secret, so nothing
generated is published. Unit tests for both refusals and the Argo order;
VALUES.md regenerated; tools/check.sh passes.
2026-11-20 01:15:03 -07:00