1. Proposed title of this feature request
Resource quotas do not generate when creating a new namespace, vice a new project
 
2. What is the nature and description of the request?
Our customer has put in place a default resource quota that is part of the default project template, per DISA STIG requirements. This is a security measure intended to limit the damage a rogue developer type user can do via the self-provisioner cluster role. However, we have discovered that if said user type creates a new namespace instead of a new project, the default project template does not generate that resource quota and thus the rogue developer has free reign to over-allocate resources in that namespace. We would like an option to tie namespaces to the default project template as if it were a project.
 
3. Why does the customer need this? (List the business requirements here)
This is needed to meet DISA STIG requirements.
 
4. List any affected packages or components.
OpenShift Container Platform.