Hello

I went through your spec.
It has the same problem. Once the volume is mounted the conf directory will
be empty. I would reiterate on the fact that if you want to use a volume
for conf directory then you would need to get those config files in the
volume you want to mount.

Using configmap is one way to create the config-files.
I have a chart(https://github.com/sushilkm/nifi-chart) that I use for NiFi,
you can have a look at that to understand more about it. FYI, the chart
does not puts all files like bootstrap.conf or nifi.properties to the
mounted volume.

Thanks
Sushil Kumar

On Tue, Nov 10, 2020 at 12:52 AM muhyid72 <[email protected]> wrote:

> 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/
>

Reply via email to