Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quota increase auto-approval: Backend, New CPU Threshold #4496

Closed
funtigr opened this issue Dec 12, 2024 · 1 comment
Closed

Quota increase auto-approval: Backend, New CPU Threshold #4496

funtigr opened this issue Dec 12, 2024 · 1 comment
Assignees

Comments

@funtigr
Copy link
Collaborator

funtigr commented Dec 12, 2024

Description:
After getting rid of the limits in the OpehShift and Registry, the requirements of the auto-approval has changed:

  1. 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).
  2. 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

image.png

@funtigr
Copy link
Collaborator Author

funtigr commented Jan 11, 2025

Tested it for CPU. The logic in the code for Memory is the same. There is no easy way to check the higher bounds for the Storage, so didn't check that.

@funtigr funtigr closed this as completed Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants