[stable/redis] verifying if persistence.enabled and master.persistence.path is working

[FatCache]

Describe the bug question
A clear and concise description of what the bug is.
In the Minikube local cluster, I have set persistence.enabled to false. I also have master.persistence.path param set to /host/ as a precautionary measure. This /host is a mounted directory from minikube mount C:/User/<username>/Documents/minikube:/host/

Why I did those? In my attempt to fix this issue:

Version of Helm and Kubernetes:
kubernetes 1.15.5
Helm 3.2.4
Minikube 1.12.1

Which chart:
Redis

What happened:
The redis-master-0 pod status is Running status but hits this eventually:

I am aware of this issue defined in the ReadMe.md 1990. Yet the pod experience of it not having write permission. This manifest pod's status to becomes Crashloopbackoff.

What you expected to happen:

1. I expect the permission to to show up even with the parameter set as mentioned in the doc

2. As the problem deals with 'appendonly'. I found a thread on stackoverflow where it is mentioned to set appendonly value to no. I expected this to be no' as well with the parameter but it is not.

For example in redis-cli I see this [I might be seeing at the wrong place, please correct me if I am wrong]:

Please note save key is empty

How to reproduce it (as minimally and precisely as possible):
Have minikube 1.12.1
minikube start --driver=docker --kubernetes 1.15.5
helm install redis setup/redis/chart --set usePassword=false --set persistence.enabled=false

kube get pod => gives us pod is running status
.... eventually the pod hits status Crashloopbackoff

Anything else we need to know:
Working on corporate computer with two account - admin and nonadmin. Docker is running as admin whereas minikube runs as non admin. In Windows 10 enivornment.

On the side if it helps. I also have Kafka with exact same parameter running with mountPath set to /host, this also errors out:

`Error executing 'postInstallation': EACCES: permision denied, mkdir '/bitnami/zookeeper/data'

• on kubectl describe pod redis-master-0
  
  

• the entry of redis.conf
  

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity.