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 Feb 22, 2022. It is now read-only.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature
Version of Helm and Kubernetes: Any
Which chart: Grafana
What happened: Actually the chart allows only to set secret values by inserting them in the grafana.ini value (that will go in the ConfigMap) or setting them in extraEnv value (that will go in cleartext as env vars).
What you expected to happen: I Expect to be able to configure secret values using Kubernetes Secrets
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered:
SharpEdgeMarshall
changed the title
Grafana could not set secret env vars
Grafana could not set secret values in a safe way
Feb 15, 2018
This doesn't work anymore. The change to env from extraEnv only allows you to reference key/values from the values file. There's no way to do a secretKeyRef.
{{- range $key, $value := .Values.env }}
- name: "{{ $key }}"
value: "{{ $value }}"
{{- end }}
Is this a request for help?: No
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature
Version of Helm and Kubernetes: Any
Which chart: Grafana
What happened: Actually the chart allows only to set secret values by inserting them in the
grafana.ini
value (that will go in the ConfigMap) or setting them inextraEnv
value (that will go in cleartext as env vars).What you expected to happen: I Expect to be able to configure secret values using Kubernetes Secrets
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: