*Goal: * Provide a more seamless user experience for customers using both OpenShift and RH Quay

Problem:
Red Hat Quay provides a completely separate user experience from OpenShift even though applications running on OCP may be depending on images coming from RH Quay. Because of this disconnected nature users do not have a combined view of how images are being used by their applications.

Why is this important:

Makes Quay the best choice for a registry choice for OpenShift customers running more than one cluster
Allows OpenShift to take advantage of Quay's enterprise registry features without users having to learn two management environments

Dependencies (internal and external):
OpenShift Auth
OpenShift Console

Prioritized epics + deliverables (in scope / not in scope):

As a user on Quay UI:

• I can seee what clusters are running a specific tag
• Quay will Warn/prevent me from deleting a tag that is running on a cluster
• Quay storage pruning is done intelligently based upon runtime tag data

As a user on OpenShift UI:

• I can quickly navigate thru and pick images in Quay for my Pods (Deployment, StatefulSet, Job, etc)
• I can see image manifest data
• I can initiate image builds on RH Quay builders to reduce load on my OpenShift cluster
• If my Pod does not restart due to missing image, I can restore via Time Machine feature

Estimate (XS, S, M, L, XL, XXL): L

*Previous Work: *
None

Open questions:
Some open design questions about how similarly named projects across multiple OCP clusters should be represented within Quay
Some research should be done on additional developer use cases that haven't been considered