Make de NFS provisioner configuration optional

[rpsene]

As an user deploying my own cluster I would like to avoid getting the NFS provisioner configured out of the box without explicitly setting it via vat.tf. In a production deployment I will probably use an already existing or a new NFS server and will include some customization for my deployment to meet some requirements.

I had to execute the following before installing a customized one:

oc delete all -l app=nfs-client-provisioner -n nfs-provisioner
oc delete project nfs-provisioner

[yussufsh]

https://github.com/ocp-power-automation/ocp4-upi-powervs/blob/master/variables.tf#L393-L397 If you do not set any value or something other than "nfs" then the automation will not create an additional volume or configure storage for you.

[rpsene]

It should not even install the provider if not explicitly required by the user. For instance, I didn't set any NFS parameter and when I was about to install a custom provider I had to first remove what was installed. All NFS related items should be installed only if the user set this as true.

[yussufsh]

Can you please provide more information as what NFS resources were created when you did not set storage_type to "nfs" (this is by default)?

This is the o/p from a HA cluster on PowerVS which does not use NFS storage configurations:

# oc get project nfs-provisioner
Error from server (NotFound): namespaces "nfs-provisioner" not found

[bpradipt]

@rpsene @yussufsh is this still relevant or can be closed ?

[rpsene]

@bpradipt this is one the "saving time" options that we need to address. The NFS server can be set in a new VM, outside the Bastion and be configured in parallel. Making it option is still a feature request to give the user the option to enable it or not, or even use something already available.