As a Quay administrator,
I want the Quay Operator to store the configuration it manages in its own configuration file,
So that any changes made using the Quay-Config application do not break my deployment.

Notes:

• Currently, the configuration file and all certificates are stored in a single secret on OpenShift/k8s.
• The secret is a set of key-value pairs, where the key is the filename and the value is the base64 encoded file.
• I would suggest using the filename "config-operator.yaml" as it will be read after the base "config.yaml" and make it obvious what's managing that configuration file.
• Any configuration values managed by the Quay-Operator should be stored in that file.