Customer Problem: As of today users in Quay have very little control to contain unbounded growth of storage consumption and utilization of the registry. As every user is allowed to create new organizations and new repositories in at least their home organization there is practically no limit to storage growth. This makes it very hard for a service owner of a Quay registry to define SLAs and maintain a certain budget. It is impractical for a service owner or administrator to work directly with Quay tenants to make them aware and reduce their system utilization. At this point even well-behaving tenants don't know when they become a noisy neighbor in the platform.

Goal: Contain registry growth and utilization focussing on storage consumption.

Why is this important

• many customers are running Quay as a shared service used by many internal and external customers that they don't have direct communication with
• on-prem Quay customers are subject to capacity limits of their environment, specifically regarding backend storage consumption
• contain growth and provide SLAs with confidence individual consumption of Quay tenants

Prioritized deliverables:

Quota management

1. As a Quay superuser I can define a storage quota while creating a new organization
2. As a Quay superuser I can override storage quotas for existing organizations
3. As a Quay organization owner I can configure two alerting thresholds on the storage quota that will cause Quay to send notifications or emails when said thresholds are reached
4. As a Quay superuser I can define a system-wide default storage quota that is applied to every new organization created by any tenant.
5. A owner of an organization to which a system-wide default quota has been applied cannot change the quota, only superusers can (as per 2.)
6. A storage quota of 0 means effectively no (additional) images can be pushed
7. Absence of a storage quota means unlimited storage for this organization

Quota enforcement

1. When a organization reaches its storage quota limits all subsequent pushes will be denied until enough images are deleted to move consumption between the quota threshold

Dependencies (internal and external):

• PROJQUAY-253

Estimate (XS, S, M, L, XL, XXL):  TBD

Previous Work: 

• TBD

Open questions:
*