Goal: Enhance the Application Developer Experience on OpenShift when working with Quay.

Why is this important: When images are pushed / pulled to and from Quay to run software on OpenShift there is a rich set of APIs available via Quay that currently is not used but could significantly reduce churn, frustration, errors and surprises when working with images stored outside of OpenShift.

Benefit hypothesis: Developers and Users prefer using Quay and OpenShift for explorative prototype development and regular application deployment / maintenance.

Prioritized deliverables:

• cluster admins get more insight, control and security in regards to container images running on their clusters
• cluster admins get a unified role-based accress control between OpenShift users and Quay users to easily enforce security boundaries of workloads
• openshift users leverage a UI in order to streamline the experience of instantiating containers