Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4816

Enforce API rate limit on quay registry from UI or through quay API

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Quay
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

      1. Proposed title of this feature request
      Enforce API rate limit on quay registry from UI or through quay API

      2. What is the nature and description of the request?
      Currently, the rate limit for API calls on the quay instance can be set to either 30s using FEATURE_RATE_LIMITS or default 300 per second when FEATURE_RATE_LIMITS is not set. The customer would like the ability to set rate limits per organization directly from the UI or through API calls.

      3. Why does the customer need this? (List the business requirements here)
      This will allow the customer to modify the rate limit on an organizational level based on usage or specific requests. Without having this safeguard quay API, excessive usage impacts the registry's overall usage.

      4. List any affected packages or components.
      FEATURE_RATE_LIMITS

            DanielMesser Daniel Messer
            rhn-support-ibazulic Ivan Bazulic
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: