-
Story
-
Resolution: Done
-
Critical
-
None
-
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