From a user's perspective, if they are not familiar with Kubernetes, the easiest way to manage all the security related resources would be though the OSD UI. Even if someone is familiar with K8s, creating the resources in OSD is much more easier than creating the CRs or configuring the secret directly.

But with how the operator works today, it is highly risky to create/modify any resources via OSD as every time the security job is run, it overwrites/deletes everything done by the user via the OSD.

We need a way so that when the security job is run, it preserves all the existing resources or at least recreates it.