charts/authentik: avoid mounting envFrom secret if secret configuration disabled - #497
Merged
rissson merged 1 commit intoJul 28, 2026
Conversation
If a user wants to configure authentik by only providing environment variables (eg: .Values.global.env), disabling the secret creation and not setting existing secret doesn't stop the envFrom from being templated in the deployments. Sourcing configuration from env only could be useful to source config from different secrets (I'm using CNPG and I source the PG passwords from a specific secret). Signed-off-by: Baptiste ROUX <arte.but.posix@gmail.com>
rissson
approved these changes
Jul 28, 2026
rissson
enabled auto-merge (squash)
July 28, 2026 11:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a user wants to configure authentik by only providing environment variables (eg: .Values.global.env), disabling the secret creation and not setting existing secret doesn't stop the envFrom from being templated in the deployments.
Sourcing configuration from env only could be useful to source config from different secrets (I'm using CNPG and I source the PG passwords from a specific secret).