Closed zrankinOCEUS closed 9 months ago
Checked and found the config map RELEASE-grafana
getting rendered, created and mounted correctly with the defined contents. The resulting file /etc/grafana/grafana.ini
in the grafana
container is correct including custom modifications. So far, I cannot confirm the described behaviour.
Used a trivial customization (grafana chart 7.0.11 as in KPS 55.0.0):
grafana:
grafana.ini:
auth.generic_oauth:
enabled: false
name: OAuth
analytics:
check_for_updates: false
Checked and found the config map
RELEASE-grafana
getting rendered, created and mounted correctly with the defined contents. The resulting file/etc/grafana/grafana.ini
in thegrafana
container is correct including custom modifications. So far, I cannot confirm the described behaviour.Used a trivial customization (grafana chart 7.0.11 as in KPS 55.0.0):
grafana: grafana.ini: auth.generic_oauth: enabled: false name: OAuth analytics: check_for_updates: false
Ah, you are correct, this was an instance of PEBKAC. Thank you for your time and support.
My mistake, for any other noobies that might stumble upon this, was nesting grafana.ini within data as such:
grafana:
data:
grafana.ini:
auth.generic_oauth:
key:value
Closing as completed.
Describe the bug a clear and concise description of what the bug is.
This is an issue reopening the following issue:
https://github.com/prometheus-community/helm-charts/issues/1337
I have followed a similar structure where within the "grafana:" label I added a grafana.ini section and auth.generic_oauth within the ini.
`grafana: grafana.ini: auth.generic_oath: