[rhacs-docs-4.6] fix: add ScannerV4 PVC size and storageClassName options

modules/central-configuration-options-operator.adoc

@@ -202,9 +202,15 @@ Ensure that this value does not exceed the maximum number of connections support
 | Use this parameter to override the default resource requests for Scanner V4 DB.
 
 | `scannerV4.db.persistence.persistentVolumeClaim.claimName`
-|The name of the PVC to manage persistent data for Scanner V4.
+| The name of the PVC to manage persistent data for Scanner V4.
 If no PVC with the given name exists, it is created. The default value is `scanner-v4-db` if not set. To prevent data loss, the PVC is not removed automatically when Central is deleted.
 
+| `scannerV4.db.persistence.persistentVolumeClaim.size`
+| The size of the PVC to manage persistent data for Scanner V4.
+
+| `scannerV4.db.persistence.persistentVolumeClaim.storageClassName`
+| The name of the storage class to use for the PVC. If your cluster is not configured with a default storage class, you must provide a value for this parameter.
+
 | `scannerV4.indexer.nodeSelector`
 | If you want this component to only run on specific nodes, you can use this parameter to configure a node selector.
 

modules/central-services-public-config.adoc

@@ -330,9 +330,15 @@ The following table lists the configurable parameters for Scanner V4.
 | Parameter | Description
 
 | `scannerV4.db.persistence.persistentVolumeClaim.claimName`
-|The name of the PVC to manage persistent data for Scanner V4.
+| The name of the PVC to manage persistent data for Scanner V4.
 If no PVC with the given name exists, it is created. The default value is `scanner-v4-db` if not set. To prevent data loss, the PVC is not removed automatically when Central is deleted.
 
+| `scannerV4.db.persistence.persistentVolumeClaim.size`
+| The size of the PVC to manage persistent data for Scanner V4.
+
+| `scannerV4.db.persistence.persistentVolumeClaim.storageClassName`
+| The name of the storage class to use for the PVC. If your cluster is not configured with a default storage class, you must provide a value for this parameter.
+
 | `scannerV4.disable`
 | Use `false` to enable Scanner V4. When setting this parameter, the StackRox Scanner must also be enabled by setting `scanner.disable=false`. Until feature parity between the StackRox Scanner and Scanner V4 is reached, Scanner V4 can only be used in combination with the StackRox Scanner. Enabling Scanner V4 without also enabling the StackRox Scanner is not supported. When you set this parameter to `true` with the `helm upgrade` command, Helm removes the existing Scanner V4 deployment.
 

modules/secured-cluster-configuration-options-operator.adoc

@@ -164,9 +164,15 @@ Use Scanner configuration settings to modify the local cluster scanner for the i
 | Use this parameter to override the default resource requests for Scanner V4 DB.
 
 | `scannerV4.db.persistence.persistentVolumeClaim.claimName`
-|The name of the PVC to manage persistent data for Scanner V4.
+| The name of the PVC to manage persistent data for Scanner V4.
 If no PVC with the given name exists, it is created. The default value is `scanner-v4-db` if not set. To prevent data loss, the PVC is not removed automatically when Central is deleted.
 
+| `scannerV4.db.persistence.persistentVolumeClaim.size`
+| The size of the PVC to manage persistent data for Scanner V4.
+
+| `scannerV4.db.persistence.persistentVolumeClaim.storageClassName`
+| The name of the storage class to use for the PVC. If your cluster is not configured with a default storage class, you must provide a value for this parameter.
+
 | `scannerV4.indexer.nodeSelector`
 | If you want this component to only run on specific nodes, you can use this parameter to configure a node selector.