The storage backend used for persisting the data from OpenEBS volumes should be made flexible and configurable. For example, in addition to supporting hostdirectory, additional options like - new disks, cloud disks etc., should be supported.

as part of enabling the openebs, admin can run an additional command like below to specify/configure the storage backend.

kubectl apply -f openebs-config.yaml

the configuration will be saved as "custom resource" objects in k8s. maya-storageagents (aka maya-agents) running on the minions will watch for these custom-resources and take appropriate actions - like creating/modifying/deleting storage backends for the openebs volumes. monitoring the storage-backends, capturing the usage metrics etc.,