Hi,
We’ve docker compose running environment of grafana, where the volumes are mounted as grafana_data:/var/lib/grafana and it consists of the grafana.db file and folders for alerting / plugins / csv / png etc.
Now the plan is to move this to EKS via helm chart - need some assistance here on ways to migrate/export the above folders entirely along with .db to RDS. Is there any way we can migrate and manage entirely with RDS.
As other alternative would be to use a EBS/EFS with EKS by mounting the backup grafana data (which we want to avoid)
thanks for this. I’m also concerned about the folders, does it also take care of that?
The best way is to test it in dev env (of course backup, backup, backup first). I don’t have idea what do you mean with term “folders” - of course folders on filesystem can’t be “migrated” to DB, but dashboard folders (logical organizations of folders) are in the DB already.
Context:
I’m concerned about the folders on filesystem which you can see below in the current setup (along with grafana.db which can be migrate to RDS ) . I’m looking for ways which supports export/migration of below so that it can entirely be managed with RDS. If not. then only solution it seems to be is using a EFS/EBS with EKS with below data mounted on it.
ls -ltrh /var/lib/docker/volumes/grafana_data/_data/
total 878M
drwxr-xr-x 3 syslog root 4.0K Jul 3 12:52 alerting
drwx------ 2 syslog root 4.0K Jul 3 12:52 csv
drwx------ 2 syslog root 4.0K Jul 3 12:52 pdf
drwxr-xr-x 8 472 root 4.0K Jul 3 12:52 plugins
drwx------ 2 syslog root 4.0K Jul 3 12:52 png
-rw-r----- 1 syslog root 878M Jul 17 11:05 grafana.db
Each container/pod should has own local filesystem, where you should install (e. g. via env variable) the same set of plugins and their versions).
No idea why you have other folders, so just setup them as you need. I hate EFS, but you may be fan of it (and all K8S volume issues).
