Goal
- Develop a new PatternFly based UI to replace Quay's existing Angular web interface
- Host this new UI as a separate deployment that talks to Quay via its API layer
- Make this UI usable via container-only Quay, Quay running on OpenShift, and hosted Quay behind HAC.
- Full details on the UI breakdown can be found here
Why is this important?
- The underlying codebase is fragile and relies on very old Javascript libraries that are challenging to use and impossible to keep up to date with security patches.
- Quays visual appearance is disconnected from the rest of the Red Hat Hybrid Cloud product portfolio, specifically OpenShift
- the current UI leaves a lot of potential benefits on the table to help administrators with intuitive and effective management, especially batch actions
- Quay will get numerous new user-facing features in the future that we do not want to have to implement in the old Angular UI framework
High-level acceptance criteria
The UI...
- has 1:1 feature parity with the current Quay web UI, not visual parity
- is modular enough to be used in standalone Quay deployments using containers on RHEL, in pods on OpenShift managed by the operator or as part of HAC on console.redhat.com
- aligns with the visual style and language of OpenShift Container Platform and ACM
- is supported on all modern browsers
- does not introduce dependencies with unfixed CVEs
Open questions:
- relates to
-
PD-1254 [Quay] Quay UI rewrite in PatternFly - Phase 1 MVP
- New
-
PROJQUAY-1245 Superusers can see and control all content
- Closed