When tweaking VSM to use ROX volumes and the custom storageclass to enable shallow-copy of snapshots to be used by volsync.

When doing this, we must create the dummy pods with the matching securityContext fields as the application pod to ensure that the pod can be created. Additionally, volsync replicationsource pods run under a unique SCC which breaks the VSM workflow by default when using ROX. I am unsure what is causing this, needs investigation and collaboration with the volsync team.