StorageOS 2 and OKD 4.4 volumes created after installation not visible in dashboard and not spread across nodes

[storageos]

StorageOS 2 and OKD 4.4 volumes created after installation not visible in dashboard and not spread across nodes

[Arau]

Even though most of the questions have been addressed through the Slack channel, we would like to add information to the issue.

The StorageOS GUI segments the Volumes following the Kubernetes namespaces or in this case the OpenShift projects where the PVC is placed. In the GUI, there is picker selector at the top left to choose what namespace is the current view of the Volumes page. See the image attached.

Regarding the replicas, StorageOS has a placement algorithm that doesn't allow the master and its replicas to be in the same instance. A volume with 2 replicas requires 3 nodes, one for the master and one for each replica. Otherwise, if that requirement is not met, the volume provisioning will fail.

I would recommend using the dynamic provisioning functionality that StorageOS provides by provisioning PVCs. When a PVC is provisioned, StorageOS provisions a Volume and maps it with a PV. Creating a Volume from the GUI does not create a PVC or PV. That procedure is manual. Therefore we would recommend to use a PVC and let the automation work for you.