Add secretEnvironment maps to charts #47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lain/separate-secret-environment-20261013065722"
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?
Adds a separate secretEnvironment map to all charts that expose container environment variables, including Stalwart and optional Bulwark. A non-empty map creates a chart-managed Kubernetes Secret and the workload imports it using envFrom.secretRef; regular environment maps remain unchanged. Stalwart keeps extraSecretEnv working for compatibility.
Chart versions are bumped. Existing values are intentionally not auto-migrated: users must move each sensitive key/value into secretEnvironment and remove it from its old environment or chart-specific setting. Restart the workload after changing the map, because environment variables sourced from a Secret are read at container start.
This keeps the value out of Deployment and Pod specs, but Kubernetes Secret access and Helm release storage still need appropriate RBAC and protection.