The following pods do not have the default SCC's defined by OCS Operator:

 NAME: ocs-operator-68b59c8976-6qkdf

 SCC: anyuid

The SCC (Security Context Constraints) for OCS pods should not be changed to default.

If the SCC's are changed, this can result in existing Ceph volumes giving access denied when trying to read/write.

----------------------------

The following pods have scc set to 'anyuid':

NAME: ocs-operator-68b59c8976-6qkdf:

 SCC: anyuid

The scc (Security Context Constraints) for OCS pods should not be changed to 'anyuid'

after the initial deployment of OCS.

This can cause the problem as the PV may be already configured to a different User ID and

changing scc to anyuid will cause the pod to run with different UID.

This can result in existing Ceph volumes giving Access denied when trying to read/write.

While it will allow creating new volumes.

Currently, the scc change is not acceptable, as the OCS pods cannot handle it.