Lack of persistency in /node-conf path about redis HOT 3 CLOSED

I think this should not be the case since the object to add this was to make the pod more stable by moving the cluster configuration into a persistent volume.

Can you elaborate more this needs to be fixed.
@guychekarev

from redis.

@shubham-cmyk Thanks for your response. As I understand you were meaning to put /node-conf on a dedicated PVC, but in the Dockerfile the only volume was /data.

from redis.

@guychekarev
I just mounted the volume of the pod at location /node-conf to a PVC.
This could make the sure that node.conf is not lost but I am not sure on the container restart.

I think you can open a PR that could add another VOLUME["/node-conf"]

Let's see whether that could solve the problem

from redis.