NFS Mount paths don't mount unless the directories exist about spm-kubernetes

[tidridgej]

Hi @andreyzher I have checked these changes on our OpenShift cluster hosted in AWS.
Dynamic provisioning for nfs worked without any issues, so this should be good to merge

[cnrmrph]

Documentation has been added in the December release that clarifies that the directories must be present prior to deploying MQ with NFS.

[niambhscullion12]

Folks, we'll re-open this based on the call today is there anything friendlier we can do here.
N..

[andreyzher]

Hi @meathead23

We have a candidate fix for this, but could use your assistance in verifying before it is merged, as we don't have access to any AWS environments.

The code is on the nfs-paths branch.

I have verified on a standalone NFS server (using the pre-defined PersistentVolumes) and using IBM Cloud File Storage using the dynamic provisioning.

To facilitate this change, there are 2 new properties being added to the MQ configuration:

• global.mq.security.initVolumeAsRoot (boolean) - required to be able to initialise the directory structure, if it doesn't already exist.
• global.mq.multiInstance.useDynamicProvisioning (boolean) - required to use dynamically provisioner volumes using the storage class defined by global.mq.multiInstance.storageClassName

To use the dynamic provisioning capabilities in a multi-zone cluster, you may need to create a custom storage class with the volumeBindingMode attribute set to WaitForFirstConsumer to make sure that the storage is provisioned in the same zone as the node on which the corresponding pod has been scheduled.

[meathead23]

Hi @andreyzher that's excellent, I'll see if i can gt someone to have a look at this next week, thanks a lot!

[andreyzher]

Hi @meathead23, @tidridgej

The above changes have been included in the 21.5.0 release.

Thank you for your support. If you have any further issues on this topic, feel free to reopen this issue or create a new one.

Regards

andreyzher