;
> Today's Topics:
>
> 1. Re: Reducing toil in resource quota bumping (Andrew Feller)
>
>
>--
>
>Message: 1
>Date: Tue, 4 Sep 2018 09:08:41 -0400
>From: Andrew Feller
>
: Reducing toil in resource quota bumping (Andrew Feller)
--
Message: 1
Date: Tue, 4 Sep 2018 09:08:41 -0400
From: Andrew Feller
To: users@lists.openshift.redhat.com
Subject: Re: Reducing toil in resource
Yeah, we have heterogenous trust levels between production and
non-production environments. This discussion was focused solely on
non-production environment where project default template is minimal
footprint and system administrators are in line for increasing project
resource quotes per
On Sep 4, 2018, at 8:30 AM, Andrew Feller wrote:
While that is a fair assessment of the situations where this pain point
arises, there should be a better option for facilitating #3 without
allowing #1 or #2 as this is a common problem disrupting both sides of the
situation.
Knee jerk thought
While that is a fair assessment of the situations where this pain point
arises, there should be a better option for facilitating #3 without
allowing #1 or #2 as this is a common problem disrupting both sides of the
situation.
Knee jerk thought would be to modify the ProjectRequest API to allow
Ultimately you need to ask what you are trying to prevent:
1. a user from accidentally blowing up the cluster
2. malicious users
3. an application breaking at runtime because it needs more resources than
it is allotted
The second one is more what we've been discussing here - being draconian up
Thanks for the feedback Jessica!
Limiting # of projects users can create is definitely one of the things
expected, however the question was mostly focused on reducing toil due to
changing resource quotas for projects. The idea with option #1 was
restricting devs to 1 project with heftier
On Thu, Aug 30, 2018 at 8:18 AM Andrew Feller wrote:
> 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
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
