When mapping a VMware datastore to an OpenShift storage class, the user should be able to select the volume mode (Volume, Block) and the access mode (ROW, RWO, RWX). The availability of the modes depends on the storage provisioner, and each mode may enable some features in Kubevirt.

The implementation will happen in 2 phases:

1. Smart default - The operator has a list of supported volume and access modes for all the provisioners as custom resources. The controller picks the modes with highest priority, if no volume or access mode is provided in the mapping. The UI doesn't implement anything, letting the controller use the "smart" default.
2. User selection - The UI implements a component to allow selecting the volume or access mode during the mapping, allowing the user to override the default. The "smart" default is pre-selected and the lists of modes are ordered by priority.
3. Validation rules - The validation service leverages the Provisioner CRs to provide plan-level rules. When a plan is authored, the validation service can provide concerns for the chosen destination storage classes.