Goal: Enhance Quay Operator with additional use cases beyond simple "Day 2" cases

Problem:
With Quay 3.3, the Quay Operator will work concurrently with Quay ConfigTool and handle simple Day 2 operations (scale out, upgrades). We need to add more intelligence to the operator to be more proactive and deal with more sophisticated challenges.

Why is this important: 
Evolving the Quay Operator will continue to provide the lowest operating cost for Red Hat Quay,

Dependencies (internal and external):
None

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

• As the Quay Operator, I want to be able to proactively identify when there are performance issues with image pulls/pushes
• As the Quay Operator, I want to be able to manage storage on cloud environments to leverage intelligent tiering and pricing models
• As the Quay Operator, I want to be able to resolve minor runtime issues such as the loss of some application servers
• As the Quay Operator, I want to interoperate with the AppSRE DBA Operator to assist with the upgrading of Quay when complex schema migrations are required.

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

Previous Work: 
Quay Operator

Open questions:

• TBD