K-C14 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Under Argo CD the chart renders with helm template, where lookup returns nothing, and Argo maps Helm's hooks its own way. Found by reading the templates (2026-11-19), not yet run:
The webmail's app and OAuth client secrets (templates/webmail.yaml) and the metrics password (templates/server/metrics.yaml) are generated fresh on every render: the app never shows Synced, and every sync signs every webmail user out. existingSecret avoids it, but the defaults walk into it.
pre-install and pre-upgrade both become PreSync and pre-rollback is dropped. The seed Job runs on every sync (a no-op on a seeded store), and on a first install the upgrade Job (weight -10) runs before the seed (weight -5), against an empty store.
Work:
A value, or a documented rule, that makes the chart refuse to render generated secrets and require existingSecret instead.
The upgrade Job a clean no-op on a store that isn't seeded yet.
Argo CD hook and sync-wave annotations next to Helm's, so the order is the same under both. That includes the hook NetworkPolicies from #34 (-hooks-deny-all, -hooks-jobs): under Argo they become PreSync with HookSucceeded, which still works; give them a wave before the Jobs.
Check the rendered manifests on the release page for the same problems (anyone using kubectl apply).
Flux's helm-controller runs real Helm, so hooks and lookup behave there; its 5-minute default timeout is K-D9's to document.
Done when
K-L10 is green on Argo CD and Flux with selfHeal on
No secret changes between two syncs of the same values
**K-C14** · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Under Argo CD the chart renders with `helm template`, where `lookup` returns nothing, and Argo maps Helm's hooks its own way. Found by reading the templates (2026-11-19), not yet run:
- The webmail's app and OAuth client secrets (`templates/webmail.yaml`) and the metrics password (`templates/server/metrics.yaml`) are generated fresh on every render: the app never shows Synced, and every sync signs every webmail user out. `existingSecret` avoids it, but the defaults walk into it.
- `pre-install` and `pre-upgrade` both become PreSync and `pre-rollback` is dropped. The seed Job runs on every sync (a no-op on a seeded store), and on a first install the upgrade Job (weight -10) runs before the seed (weight -5), against an empty store.
Work:
- A value, or a documented rule, that makes the chart refuse to render generated secrets and require `existingSecret` instead.
- The upgrade Job a clean no-op on a store that isn't seeded yet.
- Argo CD hook and sync-wave annotations next to Helm's, so the order is the same under both. That includes the hook NetworkPolicies from #34 (`-hooks-deny-all`, `-hooks-jobs`): under Argo they become PreSync with HookSucceeded, which still works; give them a wave before the Jobs.
- Check the rendered manifests on the release page for the same problems (anyone using `kubectl apply`).
Flux's helm-controller runs real Helm, so hooks and `lookup` behave there; its 5-minute default timeout is K-D9's to document.
**Done when**
- K-L10 is green on Argo CD and Flux with selfHeal on
- No secret changes between two syncs of the same values
jcoffey-dev
added this to the 27.1 milestone 2026-11-20 06:17:04 +00:00
Chart half merged in #40: generateSecrets: false, and Argo CD hook annotations (hook NPs -30, upgrade -25..-20, seed -15/-10, egress check PostSync). The release manifests contain no Secret. Not ticked yet: done when K-L10 is green under Argo CD and Flux with selfHeal on.
Chart half merged in #40: `generateSecrets: false`, and Argo CD hook annotations (hook NPs -30, upgrade -25..-20, seed -15/-10, egress check PostSync). The release manifests contain no Secret. Not ticked yet: done when K-L10 is green under Argo CD and Flux with selfHeal on.
Argo CD, with generateSecrets: false and the Secrets made first. The app stays Synced across hard refreshes with no new sync and no Secret change. The hook order holds: upgrade check, then seed, then the rest. The crossing's refused sync leaves the store untouched.
Flux, with the chart's own generated Secrets. They are unchanged across the upgrade, because Helm's lookup works there.
Tested under both controllers in inbuxa/inbuxa-k8s-lab#38 (K-L10).
- **Argo CD**, with `generateSecrets: false` and the Secrets made first. The app stays Synced across hard refreshes with no new sync and no Secret change. The hook order holds: upgrade check, then seed, then the rest. The crossing's refused sync leaves the store untouched.
- **Flux**, with the chart's own generated Secrets. They are unchanged across the upgrade, because Helm's `lookup` works there.
Ticked on #14.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
K-C14 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)
Under Argo CD the chart renders with
helm template, wherelookupreturns nothing, and Argo maps Helm's hooks its own way. Found by reading the templates (2026-11-19), not yet run:templates/webmail.yaml) and the metrics password (templates/server/metrics.yaml) are generated fresh on every render: the app never shows Synced, and every sync signs every webmail user out.existingSecretavoids it, but the defaults walk into it.pre-installandpre-upgradeboth become PreSync andpre-rollbackis dropped. The seed Job runs on every sync (a no-op on a seeded store), and on a first install the upgrade Job (weight -10) runs before the seed (weight -5), against an empty store.Work:
existingSecretinstead.-hooks-deny-all,-hooks-jobs): under Argo they become PreSync with HookSucceeded, which still works; give them a wave before the Jobs.kubectl apply).Flux's helm-controller runs real Helm, so hooks and
lookupbehave there; its 5-minute default timeout is K-D9's to document.Done when
Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Chart half merged in #40:
generateSecrets: false, and Argo CD hook annotations (hook NPs -30, upgrade -25..-20, seed -15/-10, egress check PostSync). The release manifests contain no Secret. Not ticked yet: done when K-L10 is green under Argo CD and Flux with selfHeal on.Tested under both controllers in inbuxa/inbuxa-k8s-lab#38 (K-L10).
generateSecrets: falseand the Secrets made first. The app stays Synced across hard refreshes with no new sync and no Secret change. The hook order holds: upgrade check, then seed, then the rest. The crossing's refused sync leaves the store untouched.lookupworks there.Ticked on #14.