Feature Overview (aka. Goal Summary)  

Allow LVMS users to configure certain options of the StorageClasses it creates. 

Goals (aka. expected user outcomes)

User should be able to configure certain aspects of the StorageClass LVMS cerates, e.g. the VolumeBindingMode 

Requirements (aka. Acceptance Criteria):

1. Add new optional attribute "storageClassOptions" on the LVMCluster.deviceClass level.  Subatributes below the options:
   1. reclaimPolicy

1. 1. volumeBindingMode

1. 1. additionalParameters: added to the parameters of the SC, ignored when its one of the LVMS owned parameters

1. 1. additionalLabels:
2. StorageClassOptions can be changed as day2 operations - any change is applied to the existing storageClass

Questions to Answer (Optional):

n/a

Out of Scope

Wiping disks after removal - removed disks will otherwise be untouched, in case there is data on non-lvm owned areas. 

Background

n/a

Customer Considerations

This has been asked for by customers, see linked RFEs

Documentation Considerations

neeed to document a hint at the VolumeBindingMode section:

When VolumeBindingMode is set to"Immediate"  this can lead to pods being unscheduable. This happens when multiple PVCs with "immediate" are created and bound to multiple different nodes, and then a single pod with access to those PVCs is deployed. As the PVs are on different nodes, the pod can not access them and thus can not be schedule. Use bindingMode "WaitForFirstConsumer" in this situation. Then all PVs are create on the host the pod is being scheduled to. 

Interoperability Considerations

none