feat (chart): add support for existing usecase secret#235
Merged
Conversation
stackit-sven
approved these changes
Feb 4, 2026
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
2 participants
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.
This pull request introduces support for referencing an externally managed Kubernetes Secret for usecase credentials, allowing teams to use the External Secrets Operator (ESO) or other solutions to manage secrets outside of Helm chart deployments. The chart will now use an existing Secret if specified, rather than creating a new one.
Support for externally managed usecase secrets:
infrastructure/README.mdexplaining how to configure the chart to use an externally managed Secret via the newusecaseExistingSecretNamevalue.infrastructure/rag/values.yamlto include the newusecaseExistingSecretNamefield undershared.secrets, with instructions for its usage.Chart logic updates for conditional Secret creation:
_helpers.tplto resolve the usecase Secret name to either the existing Secret or a generated name, depending on whetherusecaseExistingSecretNameis set.secrets.yamlto only create a new usecase Secret ifusecaseExistingSecretNameis not set, ensuring the chart does not overwrite externally managed secrets. [1] [2]