-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
In order for Compliance Operator to run the scan successfully and provide results, it needs a persistent storage available and defined in the cluster.
However it is nowhere in the documentation. While majority of our customers who deploy CO have the storage class defined, those who do not - fail and struggle wihtout clear error message.
Where: should be listed as a prereq here: https://docs.openshift.com/container-platform/4.16/security/compliance_operator/co-management/compliance-operator-installation.html
Additional information:
The actual storage is not needed for successful run of the CO, it is only required for storing the raw results. However, without having it defined, the run will fail. We are considering decoupling this operation from the main scan in this jira: CMP-1225
- is triggered by
-
CMP-1225 Decouple storage requirement from scan result processing
- New