Currently we are using the hostpath-provisioner for dynamic pv creation, however since it has limited functionality work is being done in crc-org/snc#877, crc-org/snc#869 and #4114 to install and setup lvm-operator

We need to make a decision whether to make the lvm-operator the default one and remove hostpath-provisioner, the behavior of expanding disk space using the config settingdisk-size will change if we move to lvm-operator as in that case disk-size will refer to the root partition size

to increase the space for PVs user has to use the config option persistent-volume-size

while talking with @praveenkumar he suggested the following to avoid any behavior change for users who don't want to use lvm-operator and are happy with hostpath-provisioner:

First method

1. Introduce a new config enable-lvm-operator use-lvm-operator with default value false to allow users to make a choice of which operator they want to use
2. When this config is enabled/set to true the LVMCluster CR will be created and the extra partition will be used for PV
3. When this config is disabled/set to false the root partition is extended to take up the space from the extra partition (and optionally also delete the operator installation or scale down the deployments as the operatorgroup and subscription objects are created during snc)

Second method

1. Introduce a new config enable-lvm-operator with default value false to allow users to make a choice of which operator they want to use
2. When this config is enabled/set to true the extra partition will not be merged with the root partition and user has to follow the guide on openshift docs to setup/install the LVM operator on their own
3. When this config is disabled/set to false the extra partition is merged into the root partition