Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-3203

Part I: Migrate Quay.io web presence to HAC



    • Part I - Migration of Quay.io web presence
    • False
    • False
    • Green
    • In Progress
    • 100
    • 100% 100%
    • XL
    • Hide

      Architecture defined, PatternFly development work being done for 3.8

      Architecture defined, PatternFly development work being done for 3.8
    • 0


      Epic Goal

      • Initiate the migration of the web presence of Quay.io from https://quay.io to https://console.redhat.com
      • Make hosted Quay a 'first class citizen' of Red Hat's managed services portfolio
      • Set the foundation for future-state integrations with other Red Hat services also hosted by the Hybrid Application Console

      Why is this important?

      • As an isolated website it has no technical or logical connection to the rest of Red Hat's service ecosystem
      • 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.


      1. Quay.io is available as it's own category within console.redhat.com and/or with similar offering like RHTrusted Content
      2. Existing customers log into console.redhat.com, choose Quay.io and find a similar environment to what is available currently
      3. Quay users have the ability to upgrade/downgrade their plan type from free to paid (or vice versa)
      4. Quay users can manage repositories, images and tags. This includes logs, build triggers and manifest details
      5. Quay users can see their image scanning results
      6. Quay users can manage organizations and teams
      7. Quay users can manage Application (OAuth) integrations
      8. Things we will NOT bring over from current website
        1. Applications (app registry)
        2. Tutorial
        3. Quay docs (except Swagger endpoint)

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • Users have 90% fidelity with their current website experience (with the exception of what is listed above as NOT being migrated)

      Dependencies (internal and external)

      1. Hybrid Application Console
      2. HAC Dynamic Plugins

      Open questions::

      1. Substantial number of technical concerns to be identified and sorted.
      2. Can we do this work such that we have a single UI codebase for
        1. HAC
        2. Quay running on OCP on-premise?
        3. Quay running outside of OCP on-premise?

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>


        Issue Links



              syahmed@redhat.com Syed Ahmed
              bdettelb@redhat.com Bill Dettelback
              0 Vote for this issue
              5 Start watching this issue