Description of problem:

As per the documentation, Compliance Operator cannot make any assumptions about the storage classes configured on the cluster. It will consider the default storage class for PV creation but when we check API we do have the option to specify StorageClassName.

[0] https://docs.openshift.com/container-platform/4.16/security/compliance_operator/co-scans/compliance-scans.html#running-compliance-scans_compliance-operator-scans

We need to modify the documentation to provide information on storageclassName in Scansetting.
~~~
oc explain scansetting.rawResultStorage.storageClassName
GROUP: compliance.openshift.io
KIND: ScanSetting
VERSION: v1alpha1

FIELD: storageClassName <string>

DESCRIPTION:
Specifies the StorageClassName to use when creating the
PersistentVolumeClaim to hold the raw results. By default this is null,
which will attempt to use the default storage class configured in the
cluster. If there is no default class specified then this needs to be set.
~~~