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.
It caused the YAML parser much chagrin. Those quotes around the key name are no bueno. The next line "args": also has the same issue. Seems like it may have been a bug in converting from JSON to YAML?
Version of Helm and Kubernetes:
v2.14.1 and EKS v1.12.6
Which chart: grafana
What happened: YAML parser fail, doesn't install, rolled back to 3.5.4 I believe from 3.5.6
What you expected to happen: Things installed
How to reproduce it (as minimally and precisely as possible): Just try to do a helm install grafana/stable -n grafana --namespace grafana and watch it go. Make sure do do the repo update and the delete --purge first.
Anything else we need to know: Not really.
The text was updated successfully, but these errors were encountered:
rshutt
changed the title
[name of the chart e.g. stable/chart] issue title
[stable/grafana] syntax error in deployment.yaml in grafana 3.5.6
Jun 29, 2019
Describe the bug
Today, a new helm chart for grafana was release. This was in it:
charts/stable/grafana/templates/deployment.yaml
Line 78 in 9e0d2f2
It caused the YAML parser much chagrin. Those quotes around the key name are no bueno. The next line "args": also has the same issue. Seems like it may have been a bug in converting from JSON to YAML?
Version of Helm and Kubernetes:
v2.14.1 and EKS v1.12.6
Which chart: grafana
What happened: YAML parser fail, doesn't install, rolled back to 3.5.4 I believe from 3.5.6
What you expected to happen: Things installed
How to reproduce it (as minimally and precisely as possible): Just try to do a
helm install grafana/stable -n grafana --namespace grafana
and watch it go. Make sure do do the repo update and the delete --purge first.Anything else we need to know: Not really.
The text was updated successfully, but these errors were encountered: