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

Transition from `QuayEcosystem` to `QuayRegistry`

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • quay-v3.4.0
    • None
    • quay-operator
    • None
    • Tarkin [Quay 187], Utapau [Quay 188]

      As a deployer with an existing QuayEcosystem, I want to transition to a QuayRegistry with minimal interaction in order to take advantage of new Quay Operator features.

      Acceptance criteria:

      • all managed components are migrated to QuayRegistry
      • all externally managed components continued to be treated external when migrated to QuayRegistry
      • no extended service downtime outside of Kubernetes load balancing / health check timeouts

              rhn-coreos-amerdler Alec Merdler (Inactive)
              rhn-coreos-amerdler Alec Merdler (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: