Has anyone found an effective way to minimize toil between developers and
system administrators regarding project resource quotas *without resorting
to letting people do whatever they want unrestrained*?

There are only 2 ideas I can see to address this issue:

   1. Removing self-provisioning access, provisioning a single project per
   developer, and giving them admin access to it.
   2. Create ClusterResourceQuota per developer restricting total resources
   allowed

I don't know how ClusterResourceQuota handle a system administrator
increasing a project's quotas for a user who is already met their total.

Any feedback is welcomed and appreciated!
-- 

[image: BandwidthMaroon.png]

Andy Feller  •  Sr DevOps Engineer

900 Main Campus Drive, Suite 500, Raleigh, NC 27606


e: afel...@bandwidth.com
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to