Add target mount for gluster block

[mjudeikis]

Adding target folder mount for gluster block to persist configuration.
Resolves: #7198
BZ: 1540080

[mjudeikis]

@datarace, is this the fix you require?

cc: @jarrpa

[datarace]

LGTM

[mjudeikis]

/retest

[SaravanaStorageNetwork]

minor comment:

/s/glusterfs-target/glusterfs-block/

[mjudeikis]

This is my question too...

Should we be following host path naming convention (as it is now) or should we do purpose based (as per suggestion).

I prefer host path naming convention for HostPath and Purpose for config/secrets/volumes as it makes debugging much easier when tracking volume names.

[jarrpa]

This is backporting an existing feature in the templates of cns-deploy, where we named it gluster-block. Regardless, this is good enough for now. It introduces some undesirable divergence between the two template locations, but that's just more incentive to consolidate them into one faster. :)

/lgtm

[openshift-merge-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[jarrpa]

@mjudeikis Can you reference "Resolves: #7198" and any relevant BZs in the initial comment / description?

[mjudeikis]

/retest

[mjudeikis]

@jarrpa done. +1 for consolidation plan ;)

[jarrpa]

/retest

[mjudeikis]

/retest

[openshift-merge-robot]

Automatic merge from submit-queue.