[bitnami/prometheus] Add environment variable support to the Prometheus Thanos container #36251
+93
−5
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.
Description of the change
Benefits
Users can mount secrets via environment variables to the container, enabling setting environment variables like
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
to securely mount existing secrets in the cluster to the container.Additionally, the secret name supporting templating is a common pattern for many secret and configmap names. It allows for dynamic configurations of the secret name, which is often useful for umbrella charts that may wrap this chart.
Possible drawbacks
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm