loki
loki copied to clipboard
grafana
loki helm-chart 3.10.0 - allow the use of existing volume claim in persistence configuration
Is your feature request related to a problem? Please describe. On some custom deployment scenarios, it is helpful to reuse an already existing persistent volume claim. One example is a case, where one would like the storage space to outlive the deployment itself if the later needs to be shutdown and recreated later.
Describe the solution you'd like
Lots of helm charts allow the use of a named persistent volume claim, usually via a value parameter existingClaim under the relevant persistence section. If it is defined, it should take precedence over the automatic provisioning.
Describe alternatives you've considered I am not aware of a way to overcome the lack of such feature with the most recent loki helm charts. It used to be possible in older helm chart versions (for example 2.16.0).
Hi, I also expected a product like Loki to have this. It would be cool, to have this feature in helm chart.
But I found a workaround. At least in the case with a single node.
@mstavrev
Just create a PVC with name storage-loki-0.
When starting, Loki will automatically connect to this stigma.
At least Ceph wit static provisioning worked for me.
Just finished setting up grafana using persistence.existingClaim, worked perfectly, then went on to setup loki but found no such setting. This issue explains why :-) Would be very useful to have the same setting for loki.
There is a work-around described on the first comment. I would prefer if it gets an official fix as we are relying on hard coding the name of the pvc, which may change at any moment as the helm devlopment progresses.
Thank you @JWebDev but this work-around didn't worked for me, Keep this thread updated if anyone finds out a way to use existing persistent volume claim (hostpath) in Loki Stack .
Guys, we need persistence settings on Loki helm chart, specially if I want to deploy it on bare metal, using storage class 😐
