Hi Sushil, Thanks for your prompt response I added my answers below for your comments
1. Are you using a deployment or a statefulset, from kubernetes perspective I would suggest you to deploy using statefulset. *Answer:* I am using deployment. It is PoC and just one replica therefore I didn’t use Statefulset 2. You need to use securitycontext and following might help you to get access to the mounted filesystems. securityContext: runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 *Answer:* I already added security context 3. conf is a special directory which has prepopulated config files, so if you want to mount a volume to conf directory then you would need to get those pre-existing files to the mounted volumes using some way for eg. confgmap as suggested in https://issues.apache.org/jira/browse/NIFI-6484 *Answer:* I already used configmap. I tired with original nifi image and also I created custom image. As you know it is depending on start.sh therefore I added some extra parameters to the scripts (start.sh, common.sh etc). The Problem is always happening for nifi.properties I attached my yaml file (from my virtualbox with NFS) for clarification (combined for all yaml files) nifi-non-secure-nfs.yaml <http://apache-nifi-users-list.2361937.n4.nabble.com/file/t893/nifi-non-secure-nfs.yaml> -- Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
