Open alysonfranklin opened 2 years ago
What's the update on this issue??
Persistence with AWS EFS is needed for Grafana. It turns out the temporary workaround is to disable the init-chown-data container via values.yml
when persistence is enabled.
initChownData:
enabled: false
helm chart version: 6.16.13
Describe the bug After installing Grafana with the below YAML, status of pod grafana is "Init:Error". This pod uses Amazon EFS persistent volume claim. On describing the pod, the error message is "Error from server (BadRequest): container "grafana" in pod "grafana-57cbcf64bd-rl49h" is waiting to start: PodInitializing".
Has anyone managed to provision grafana with aws EFS?