• Proactive Architecture
    • XL
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • 0

      Goal Summary:

      An elevator pitch (value statement) that describes the Feature in a clear, concise way. Complete during New status.

      Provide Clair as as scanning service on top of ACS CS infrastructure to other interested groups inside Red Hat. An imcomplete list of potential consumers would be Quay, Konflux and ACS CS itself.

      Goals and expected user outcomes:

      The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

      Offloading the scanner operations and maintenance is the key outcome.

      Acceptance Criteria:

      A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

      The service must be 

      • highly available and fault tolerant
      • dynamic in scale to cater to both large and small customers in a cost efficient manner
      • SRE operable (SOPs, automation, monitoring) similar to ACS CS today
      • expose a well-defined & documented API to consumers
      • ...

      Success Criteria or KPIs measured:

      A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

      • By EoQ2 2025
        • First prototype, proof of concept
        • assessment of larger technical hurdles
      • Adoption by Quay.io
      • 99.9% (TBD) SLO on availability is reached

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

      • Customer (e.g. Quay) uses the service API to request and receive scan results for container images, instead of asking a self-hosted solution
      • Konflux offering a standard task for vulnerability scans backed by the service, enabling Red Hat engineering teams to scan images without any additional tooling

      Out of Scope (Optional):

      High-level list of items that are out of scope. Initial completion during Refinement status.

      • offering the service to external parties like e.g. Red Hat customers
      • offering the service as public facing API 

              rh-ee-lcleroux Ludovic Cleroux
              rh-ee-mhess Michael Hess
              ACS Cloud Service
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: