User Story

As a user of an OpenShift Cluster i should be restricted from creating random Shared Secrets and ConfigMaps with the "openshift-" prefix

Acceptance Criteria

• no users be able to create Shared Secrets and Shared ConfigMaps with prefix that is "openshift-" unless the name the use, as well as their reference's namespace and name, are part of the pre-approved list curated in the shared resource operator
• Integration testing to verify behavior

QE Impact

• Behavior will need to be verified

Docs Impact

• Docs will need to reflect this new behavior

PX Impact

• None

Notes

• Creating namespaces with the "openshift-" prefix is already restricted. That code could be used as a precedent for this.