== Problem ==
The build service will enable every user to trigger a build, not having per-user quotas might end up in a situation where one user creates a denial of service for the rest.
Currently the build service will enforce quotas at the namespace level, but not at the user level.
=== Constraints and risks ===
* The risks of not doing anything is allowing one user to block the builds for the rest.
== Decision record ==
In progress
https://wikitech.wikimedia.org/wiki/Wikimedia_Cloud_Services_team/EnhancementProposals/Decision_record_<>_How_to_manage_quotas_in_Toolforge_Build_service
=== Direct responsible individual ===
@dcaro
== Options ==
=== Option 1 ===
Keep only the shared namespace quota.
Pros:
* No extra work needed.
Cons:
* Does not avoid a user from affecting the others.
=== Option 2 ===
Create one namespace per-user/tool
Pros:
* Each user then has it's own namespace, with their own quotas.
Cons:
* Not sure if it's possible with the current solutions (tekton), or how much modifications will it require
* Will for sure add extra maintenance costs, as those namespaces will have to be updated every time we update the system (at least tasks and pipelines for now)
** This might require changing mainain_kubeusers to create those namespaces and quotas and such
** This also complicates development/testing