A better way to handle openshift scc ?

[adrianchiris]

We should check if there is a better way to handle openshift scc.
perhaps its possible to leverage pod security admissions ?

currently we need to create service account, role and binding to an scc (usually the privileged scc) for every component that requires anything outside the restricted openshift policy.

we should see if there is a way to enforce a policy for all objects in a namespace (the namespace that network operator is deployed in)