Custom SCC can break pods if priority is 10 or higher

Issue

• After creating a custom Security Context Constraint (SCC) with priority 10 or higher, authentication for example stays degraded during upgrades until the custom SCC is removed.
• After creating a custom SCC with priority 10 or higher, whenever a pod in is deleted and a new one is spawned, the new pod stays in CreateContainerConfigError and won't start.