-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Global project quota #16671
Comments
I know it is not what you are asked for. To somehow mitigate the out of disk space issue, you could set the new project quota to ~50% of your total available space. |
In fact, we just have that on 5%, but with multiple projects managed it's sometimes easy to loose sight how to balance the overall space in between projects. If one projects run out, I can allocate some more to that, but need to remember to decrease another one with the same size. And if there are multiple admins, probably not everyone knows by heart how much the OPS teams assigned. |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
@Vad1mo, should we keep this open? I'm still looking for an option to avoid running out of space which could break the Core service. If there are other ways we could use to still do cleanup with the Harbor UI in such case, please let me know. Ideally the Core service is still up and running in such case, so we could login but obviously push should fail. |
I would love to see this feature as well. We are having a similar issue here, sometimes the scheduled cleanup jobs don't run and then our harbor gets clogged the next day. An overall Quota would not solve the issue but at least prevent a total crash of the core service and give us a chance to trigger the cleanup policies manually. |
I'd love to see a global project quota or overall disk space which would be a hard limit for all of the projects.
This would help me to match the project quotas with the backend storage, so if somebody unconsciously modify a project quota without knowing the backend's limit, we could show an error to avoid disk issues.
Recently we ran into a situation where the overall project quota size was bigger than the disk space on the backend which resulted we couldn't even log into Harbor to cleanup. (Redis: Write error saving DB on disk: No space left on device)
I imagine a new setting on the Project Quota screen to define the global limit
The text was updated successfully, but these errors were encountered: