You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
After getting rid of the limits in the OpehShift and Registry, the requirements of the auto-approval has changed:
Billy said that if we have usage more than 100% of request, the burst-quota mechanism would be auto-triggered. So we would implement our auto-approval for the case when the Usage is over 35% of Requested quota for the namespace (e.g. if we have 4 CPU cores, the combined average usage in last 2 weeks is >1.4 CPU cores, then we auto-approve one step up).
The 35% threshold is for CPU only. For Memory and Storage he asked to look into previous tickets, where he provided limits for them (he says they are based on Requests (not limits) already).
I will look into old tickets and find it. Otherwise I will as
The text was updated successfully, but these errors were encountered:
Description:
After getting rid of the
limits
in the OpehShift and Registry, the requirements of the auto-approval has changed:I will look into old tickets and find it. Otherwise I will as
The text was updated successfully, but these errors were encountered: