-
Spike
-
Resolution: Done
-
Critical
-
None
-
False
-
False
-
Need to review the technical architecture behind HAC and propose a design that allows quay.io to integrate with it.
Functional requirements:
- Authentication (what is user's identity)
- Authorization (how is quay.io authorized to be part of HAC)
- Availability (How quay.io should host plugins for consumption by HAC)
Non-Functional requirements:
- Performance (how do we make sure quay.io's web presence remains fast and usable)
- Scale (how do we make sure quay.io's web presence can sustain a potentially large number of simultaneous users now that we're in HAC)
- Resilience (how do we make sure that quay.io's web presence remains available at all times)