You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
See also #424. Perhaps we could use environment variables for handling the secrets? Like AKS is doing right now:
// Environment variables used to load sensitive parts of the configuration.clientIDEnv="LOKOMOTIVE_AKS_CLIENT_ID"clientSecretEnv="LOKOMOTIVE_AKS_CLIENT_SECRET"// #nosec G101subscriptionIDEnv="LOKOMOTIVE_AKS_SUBSCRIPTION_ID"tenantIDEnv="LOKOMOTIVE_AKS_TENANT_ID"`
So finally it was decided that we expose all the env vars using the hcl variable. We create a secret out of it and then that is exposed into the grafana pod automatically.
This can be done in two ways.
One
One is by providing configs in Prometheus Operator Values file under this section:
src: https://grafana.com/docs/grafana/v6.5/auth/google/
Two
Or this can also be replaced with env var as follows:
All the values under
grafana.ini
can be replaced with env var in following format:GF_<SectionName>_<KeyName>
.src: https://grafana.com/docs/grafana/v6.5/installation/configuration/#using-environment-variables
The text was updated successfully, but these errors were encountered: